i got my 2.34 rooted and started remveing thngs i removed one to many things so i decided to put a custom rom on my sd card and flash so i did full wipe in recovery from android recovery but 2 differnt roms says signature failed aborting
leo5111 said:
i got my 2.34 rooted and started remveing thngs i removed one to many things so i decided to put a custom rom on my sd card and flash so i did full wipe in recovery from android recovery but 2 differnt roms says signature failed aborting
Click to expand...
Click to collapse
You need to unlock your bootloader..... rooting is not the same as unlocking your bootloader.
Start with the stickied post in the dev forums and read up
if you're on 2.3.4, i'd say the safest way to unlock your bootloader is by running this script right here:
http://forum.xda-developers.com/showthread.php?t=1182871
you're going to get a soft-hard brick, but don't panic. just start up in fastboot and follow the script's instructions.
after that, install CWM recovery and flash to a custom ROM, and enjoy how awesome your phone just became!
Alcapone263 said:
if you're on 2.3.4, i'd say the safest way to unlock your bootloader is by running this script right here:
http://forum.xda-developers.com/showthread.php?t=1182871
you're going to get a soft-hard brick, but don't panic. just start up in fastboot and follow the script's instructions.
after that, install CWM recovery and flash to a custom ROM, and enjoy how awesome your phone just became!
Click to expand...
Click to collapse
i got it figured out after some hair pulling...lol
Related
I have a phone on 4.1.57 running GreyBlur. The Android Version is 2.2.1
I haven't accepted any OTA updates, but I recently found out that Gingerbread is out.
What is the best way to go on about rooting the phone after the gingerbread update? Flash back to stock, then update, then root? If someone could point me in the right direction it'd be greatly appreciated.
thank you.
1) root your phone...using this guide...http://www.youtube.com/watch?v=sQVVqxvg4Go (files that you need are under description of that video..)
2) unlock bootloader...using this guide..http://forum.xda-developers.com/showthread.php?t=1136261
3) install Tenfar's CWM using this guide...http://forum.xda-developers.com/showthread.php?t=1138541
4) choose a rom and flash Via CWM
***Stay away from RSD as much as possible***
deziguy420 said:
1) root your phone...using this guide...http://www.youtube.com/watch?v=sQVVqxvg4Go (files that you need are under description of that video..)
2) unlock bootloader...using this guide..http://forum.xda-developers.com/showthread.php?t=1136261
3) install Tenfar's CWM using this guide...http://forum.xda-developers.com/showthread.php?t=1138541
4) choose a rom and flash Via CWM
***Stay away from RSD as much as possible***
Click to expand...
Click to collapse
Is RSD and CWM the same thing? I don't understand what these two are.
If I'm on 2.2.2, stock w/ root and side-loading enabled, do I skip #1?
why isn't pudding used in any of this?
yes skip #1
RSD is a flashing tool...
CWM is used for flashing too but it's much safer then RSD...
in order to unlock your phone's bootloader u have to do one step using RSD here is a pretty good video tutorial http://www.youtube.com/watch?v=H02N4p9vEg0 on how to unlock ur bootloader...
on my previous post...2nd link is referring to pudding is it not?
deziguy420 said:
1) root your phone...using this guide...http://www.youtube.com/watch?v=sQVVqxvg4Go (files that you need are under description of that video..)
2) unlock bootloader...using this guide..http://forum.xda-developers.com/showthread.php?t=1136261
3) install Tenfar's CWM using this guide...http://forum.xda-developers.com/showthread.php?t=1138541
4) choose a rom and flash Via CWM
***Stay away from RSD as much as possible***
Click to expand...
Click to collapse
1) I'm already rooted.
2) You say to stay away from RSD but to unlock the bootloader I need to use it correct?
3) I already have Tenfar's CWM.
4) Just choose a ROM that's updated with Gingerbread and Flash?
Thanks for your help
rAFTA! said:
1) I'm already rooted.
2) You say to stay away from RSD but to unlock the bootloader I need to use it correct?
3) I already have Tenfar's CWM.
4) Just choose a ROM that's updated with Gingerbread and Flash?
Thanks for your help
Click to expand...
Click to collapse
there are 2 versions of cwm. one for locked and one for unlocked. after you unlock you have to fastboot flash recovery to get the good CWM then you can flash roms properly.
RSD the 1.83 pudding
Fastboot oem unlock to unlock bootloader
fastboot flash recovery to get the unlocked CWM
CWM recovery to install roms
As long as you have not OTA to gingerbread then RSD is ok but not recommended. If youhave the OTA gingerbread then rsd will hard brick your device if you try to go back to an older build.
rAFTA! said:
1) I'm already rooted.
2) You say to stay away from RSD but to unlock the bootloader I need to use it correct?
3) I already have Tenfar's CWM.
4) Just choose a ROM that's updated with Gingerbread and Flash?
Thanks for your help
Click to expand...
Click to collapse
if you already have Tenfar's CWM..then wt r u waiting for ...go crazy and start flashing...
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
xlxcrossing said:
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
Click to expand...
Click to collapse
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
JayDaKissEP said:
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I did not use that method to flash, no. I'm assuming you mean from my PC execute the command. I did follow the instructions to install TWRP which is a custom recovery and I flashed a ZIP from TWRP for Superuser and checked it to be working which it was. (I tested Root Explorer and Terminal Emulator for root)
I was operating off the assumption that custom roms with a STOCK kernel could be flashed by booting into recovery. I went to bootloader then recovery then flashed the rom. Obviously I did something wrong since both roms wouldn't load. I will use your method of PC commands from fastboot into recovery and see where that gets me....pease let me know if this is correct or anything else I need to do....thanks a bunch.
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
xlxcrossing said:
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
Click to expand...
Click to collapse
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
ifly4vamerica said:
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
Click to expand...
Click to collapse
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
xlxcrossing said:
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
Click to expand...
Click to collapse
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Twolazyg said:
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Click to expand...
Click to collapse
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
JayDaKissEP said:
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
ifly4vamerica said:
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
Click to expand...
Click to collapse
Yeah I read all about it I'm still stuck on why if I had a stock kernel installed with a stock rom and I do a custom rom flash and as stated it doesn't touch the kernel why the rom wouldn't simply run off the stock kernel - that's what confuses me. I understand the issue of the kernel not being flashed which is obviously what happened with me. I just don't really know where I stand with what kernel to ALWAYS have loaded since if that's the thing with the issue I would want to for purposes of not doing tons of work stay away from flashing kernels and stick to flashing roms when I want to change it up. But if the STOCK kernel won't load with a custom rom which technically it should I guess I'll just have to flash a universal custom kernel and assume any rom I flash will simply use that kernel. Kind of a nightmare compared to my 4G....welcome to the world of the 3D I guess.
I guess going into recovery from hboot with the volume and power buttons wouldn't count - I have to stick with PC commands?
Didn't want to hijack that other thread, so I thought a more explicity thread might help others.
So I followed http://www.youtube.com/watch?feature=player_embedded&v=iMYMR3_Vk8I and got my phone unlocked. I'm unsure what to do next to get a "stock" phone rooted. All I want is to have my phone rooted so I can run SU apps. There are a couple options from the tool, of which I'm not sure what is what:
1. Flash a Recovery (TWRP 2.1) - Not sure what this is for, should I flash it? What does it do?
2. Kernels - Do I download a kernel like: http://forum.xda-developers.com/showthread.php?t=1762537 and Flash Kernel?
3. Perm Root - From the name this sounds like what I want... but can I run it on my freshly restored/unlocked phone? Do I need to run this after one of the above (or both) steps?
1. Yes. A recovery is, put simply, a tool that can be used to flash things to your phone (e.g. custom ROMs and mods). You will need a recovery in order to achieve permanent root, so flashing the recovery is definitely a good idea.
2. The thread that you linked to does not contain a kernel, it contains a custom ROM. Since we do not have any customized kernels for this phone yet, skip the flash kernel step entirely. You may want to go back and use it if a kernel is developed that you prefer, but for now, there are no kernels to flash.
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
polarimetric said:
1. Yes. A recovery is, put simply, a tool that can be used to flash things to your phone (e.g. custom ROMs and mods). You will need a recovery in order to achieve permanent root, so flashing the recovery is definitely a good idea.
2. The thread that you linked to does not contain a kernel, it contains a custom ROM. Since we do not have any customized kernels for this phone yet, skip the flash kernel step entirely. You may want to go back and use it if a kernel is developed that you prefer, but for now, there are no kernels to flash.
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
Click to expand...
Click to collapse
Thanks polarimetric for explaining! Hopefully your explanations and my slight quirks below can help some others.
The TWRP reflash worked fine. I had an issue with the Perm Root though... for some reason the SuperSU.zip wasn't actually getting copied over to the phone before it was rebooted into recovery. I ended up mounting the sdcard and manually copying over SU/SuperSU.zip to my sdcard. At that point I ran Perm Root again (which in my case just reboots into recovery). From there I clicked "Install" and selected the /sdcard/SuperSU.zip file. It installed and rebooted.
Successfully rooted!
More advice pleae.
polarimetric said:
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
Click to expand...
Click to collapse
I flashed a recovery yesterday since I needed to recover. After that my endlessly booting appliance booted successfully.
Now I want to Root. I tried this using the Hasoon2000 thing yet and got a "Simply Brilliant" screen when I rebooted into recovery but then got could not connect message when I tried to permanently root.
Do I need to flash a different recovery?
Wow, this thread got my hopes up til I saw it was bumped.
As of several months ago, we lost the ability to root:
http://forum.xda-developers.com/showthread.php?t=1792514
So, until an exploit is found or verizon says we can do it, we can't root.
Hesacon said:
Wow, this thread got my hopes up til I saw it was bumped.
Click to expand...
Click to collapse
Yeah, the same thing happened to me. I tried HTCDev unlock last night and it didn't work, so I was very surprised to see that as the most recent post. Now I'm extremely disappointed.
i hope i am not getting anyone elses hopes up either.... but man i am disappointed
This phone isn't even relevant anymore... I don't know why Verizon gives a **** about locking us out.
I have used windroid htc one x+ toolkit to unlock bootloader.
It shows a dialogue saying bootloader is unlocked . But in the phone it still shows a locked screen and also showing as s-off
I have root and i am able to use titanium backup.
I have also tried to flash twrp recovery.. but not able to do so.
Can somebody please point me in the right direction..
tonysimonhere said:
I have used windroid htc one x+ toolkit to unlock bootloader.
It shows a dialogue saying bootloader is unlocked . But in the phone it still shows a locked screen and also showing as s-off
I have root and i am able to use titanium backup.
I have also tried to flash twrp recovery.. but not able to do so.
Can somebody please point me in the right direction..
Click to expand...
Click to collapse
Try manually follow the instructions from htcdev and let us know which part fails........
[email protected] said:
Try manually follow the instructions from htcdev and let us know which part fails........
Click to expand...
Click to collapse
Thank you ..
I was able to flash twrp using Rom toolbox.
now I have twrp but the bootloader still shows as locked.
I tried to install a custom Rom but failed because of my own mistake.. today I will try once more to flash a Rom.
will post it's result..
I think I read somewhere that soff devices can't be unlocked..is this true
tonysimonhere said:
Thank you ..
I was able to flash twrp using Rom toolbox.
now I have twrp but the bootloader still shows as locked.
I tried to install a custom Rom but failed because of my own mistake.. today I will try once more to flash a Rom.
will post it's result..
I think I read somewhere that soff devices can't be unlocked..is this true
Click to expand...
Click to collapse
I dont think so....
Can u try using HTC dev and report back....
NOTE UNLOCKING WILL WIPE ALL UR DATA AND SDCARD STUFF FROM UR PHONE....
SO BACKUP
[email protected] said:
I dont think so....
Can u try using HTC dev and report back....
NOTE UNLOCKING WILL WIPE ALL UR DATA AND SDCARD STUFF FROM UR PHONE....
SO BACKUP
Click to expand...
Click to collapse
Sure I will try it in the evening.
You can definitely Unlock it using the HTCDEV process , I have a done this. Any ways if you are able to flash a ROM then there is no reason to get it Unlocked, more over S-OFF gives you full control over the device but again it also increases the risk of getting your phone bricked so make sure you use it wisely (knowing what you flash) , so I will say why to beg HTC for some thing they have already provided.
One more thing S-OFF device means you dont need to flash boot.img separately so you dont need to use your PC to flash roms no more.
Waiting to know about your progress on flashing the ROM ..
ethanon said:
You can definitely Unlock it using the HTCDEV process , I have a done this. Any ways if you are able to flash a ROM then there is no reason to get it Unlocked, more over S-OFF gives you full control over the device but again it also increases the risk of getting your phone bricked so make sure you use it wisely (knowing what you flash) , so I will say why to beg HTC for some thing they have already provided.
One more thing S-OFF device means you dont need to flash boot.img separately so you dont need to use your PC to flash roms no more.
Waiting to know about your progress on flashing the ROM ..
Click to expand...
Click to collapse
I have now successfully flashed a Rom..initially I tried it without flashing the boot.img and it entered a boot loop.
Then I installed flashify and flashed boot.img that came with the Rom. Then the Rom is working now.
The boot loader is still locked. Has twrp .
tonysimonhere said:
I have now successfully flashed a Rom..initially I tried it without flashing the boot.img and it entered a boot loop.
Then I installed flashify and flashed boot.img that came with the Rom. Then the Rom is working now.
The boot loader is still locked. Has twrp .
Click to expand...
Click to collapse
so you mean to say you failed to install the boot.img from the custom recovery ? well that is weird, one more thing since you were in boot loop how did you manage to install flashiffy !
if you may please include the complete flashing steps , will be helpful for my experiments.
ethanon said:
so you mean to say you failed to install the boot.img from the custom recovery ? well that is weird, one more thing since you were in boot loop how did you manage to install flashiffy !
if you may please include the complete flashing steps , will be helpful for my experiments.
Click to expand...
Click to collapse
Initially I flashed the Rom alone and it went into bootloop and all buttons became unresponsive .so I waited till the battery ran out and the phone switched off. Then I recharged , entered recovery by vol down + power button.. I had the backup there . So I restored back up.. then phone rebooted normally.. and I flashed boot.img by flashify just because I didn't know any other method... Then from recovery I wiped dalvik cache and system .. flashed the new Rom.. reeboot and fine..
Feel free to ask for any more clarification..
right been sat here trying to figure this out..
ive just unlocked by bootloader so before i start installing roms i thought ill install a custom recovert because that was what i used to do when i was on my other android phones ( ive been on the ios scene for the past 2 years or so)
so my question is how i tried following the guides some even took me to this one click installation .bat files but i dont know if its worked i have tried to reboot to recovery via adb but no luck.
i am confused with the installation guides of kernels someone please link me to some instruction for dummys.
cheers
ps i rooted by phone before i unlocked my bootloader however i didnt do a ta backup is that serious?
shaji007 said:
right been sat here trying to figure this out..
ive just unlocked by bootloader so before i start installing roms i thought ill install a custom recovert because that was what i used to do when i was on my other android phones ( ive been on the ios scene for the past 2 years or so)
so my question is how i tried following the guides some even took me to this one click installation .bat files but i dont know if its worked i have tried to reboot to recovery via adb but no luck.
i am confused with the installation guides of kernels someone please link me to some instruction for dummys.
cheers
ps i rooted by phone before i unlocked my bootloader however i didnt do a ta backup is that serious?
Click to expand...
Click to collapse
you need to use the installer for Z2 only and you need all drivers installed with the correct adb files
all can be found at developer.sonymobile.com
there is a info thread at the top of the QnA section, you may find ways to recover your device there
Envious_Data said:
you need to use the installer for Z2 only and you need all drivers installed with the correct adb files
all can be found at developer.sonymobile.com
there is a info thread at the top of the QnA section, you may find ways to recover your device there
Click to expand...
Click to collapse
thanks for the reply. I think I have done everything correctly. however one major problem I been trying to install a recovery partition and I installed [sirius][CWM Advanced Edition] PhilZ Touch {UNOFFICIAL} [20140528] using the fastboot flash recovery method which resulted in an ok but for some i cant seem to go into it, ive tried adb reboot recovery it just boots up like normal and pressing the up button during boot.
have I installed it right?
shaji007 said:
thanks for the reply. I think I have done everything correctly. however one major problem I been trying to install a recovery partition and I installed [sirius][CWM Advanced Edition] PhilZ Touch {UNOFFICIAL} [20140528] using the fastboot flash recovery method which resulted in an ok but for some i cant seem to go into it, ive tried adb reboot recovery it just boots up like normal and pressing the up button during boot.
have I installed it right?
Click to expand...
Click to collapse
xperias dont have native recovery partitions, installing to recovery partition does nothing.
recoveries for Unlocked bootloaders are stored in the ramdisk in the kernel
for locked bootloaders i do belive a small script it modded in the kernel, the recovery image is put in your /system/
what you tried installing is a custom kernel with the recovery image inside, try installing to your boot after unlocking your bootloader(if you want to which voids your warrenty)
Thanks to your explanation and a bit of research I have succeeded. Running cyonogenmod 11 now thanks bud!
Sent from my Xperia Z2 using XDA Free mobile app