What's up everybody. I've searched through the questions forum and can't seem to find a thread to help me, so...
I wanted to flash dhacker's 4.4 ROM. So first I want to make a backup of my phone pending something goes horribly wrong. I'm having issues booting into recovery. When I click on "recovery", the phone seems to restart like it's going into recovery, then I get a sleeping android bot with his belly open and a red triangle with an exclamation point in it on my screen, forcing me to reboot the phone. Any ideas?
- Is it that I don't have an updated version of CWM or TWRP? Anyone have links to working versions?
- Is it that I have the "lite" versions of said apps above and need to donate to open the recovery features?
- Is it something else and I'm just not smart enough to think of what it could be?
Thanks for the help!
LifeAsADroid said:
What's up everybody. I've searched through the questions forum and can't seem to find a thread to help me, so...
I wanted to flash dhacker's 4.4 ROM. So first I want to make a backup of my phone pending something goes horribly wrong. I'm having issues booting into recovery. When I click on "recovery", the phone seems to restart like it's going into recovery, then I get a sleeping android bot with his belly open and a red triangle with an exclamation point in it on my screen, forcing me to reboot the phone. Any ideas?
- Is it that I don't have an updated version of CWM or TWRP? Anyone have links to working versions?
- Is it that I have the "lite" versions of said apps above and need to donate to open the recovery features?
- Is it something else and I'm just not smart enough to think of what it could be?
Thanks for the help!
Click to expand...
Click to collapse
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
RikRong said:
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
Click to expand...
Click to collapse
Thanks, I'll give it a try.
I did at one point have an unlocked bootloader, but I wasn't sure whether the latest OTA updates only blocked the ability to unlock (if someone hadn't already unlocked) or if it locked back up the already unlocked ones.
LifeAsADroid said:
Thanks, I'll give it a try.
I did at one point have an unlocked bootloader, but I wasn't sure whether the latest OTA updates only blocked the ability to unlock (if someone hadn't already unlocked) or if it locked back up the already unlocked ones.
Click to expand...
Click to collapse
once the bootloader is unlocked, it cant be locked back.
Bonus. That's what I thought, something about creating a small nuclear explosion in the phone that destroys the bootloader locking resistor or something. Glad I took care of that prior to the update that shut the door on that exploit.
Something else I thought of... I'm reading that 4.4 makes it much harder to root phones. I guess we won't know until the OTA release comes out, but I'm hoping Voodoo Rootkeeper maintains root during the update like it has in the past for me in previous updates.
LifeAsADroid said:
Bonus. That's what I thought, something about creating a small nuclear explosion in the phone that destroys the bootloader locking resistor or something. Glad I took care of that prior to the update that shut the door on that exploit.
Something else I thought of... I'm reading that 4.4 makes it much harder to root phones. I guess we won't know until the OTA release comes out, but I'm hoping Voodoo Rootkeeper maintains root during the update like it has in the past for me in previous updates.
Click to expand...
Click to collapse
If your bootloader is unlocked, you don't need to maintain root. You just need to flash a SU zip in recovery.
so if i unlock my bootloader, i will still be able to receive the eventual ota 4.4 update correct?
RikRong said:
If your bootloader is unlocked, you don't need to maintain root. You just need to flash a SU zip in recovery.
Click to expand...
Click to collapse
peladoro said:
so if i unlock my bootloader, i will still be able to receive the eventual ota 4.4 update correct?
Click to expand...
Click to collapse
Yes, but you won't be able to unlock if you're system version is newer than May.
hey rikrong...as i had mentioned in another thread, found out that i am indeed able to root unlock etc...(xt925). so it's safe to say that unlocking the bootloader for obvious reasons is needed to flash roms but is not negatively affecting the phone from functioning in anyway right? sorry if these r stupid questions but just trying to understand...the only issue is warranty
RikRong said:
Yes, but you won't be able to unlock if you're system version is newer than May.
Click to expand...
Click to collapse
peladoro said:
hey rikrong...as i had mentioned in another thread, found out that i am indeed able to root unlock etc...(xt925). so it's safe to say that unlocking the bootloader for obvious reasons is needed to flash roms but is not negatively affecting the phone from functioning in anyway right? sorry if these r stupid questions but just trying to understand...the only issue is warranty
Click to expand...
Click to collapse
Yeah, sorry, I lose track of the posts. Just simply unlocking the BL should have no adverse affect on the phone, just the warranty, like you said.
hehe...ok thanks again!!!
RikRong said:
Yeah, sorry, I lose track of the posts. Just simply unlocking the BL should have no adverse affect on the phone, just the warranty, like you said.
Click to expand...
Click to collapse
RikRong said:
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
Click to expand...
Click to collapse
Hello
Please can you explain step by step how to install a cwm ? (i just unlock the bootloader)
Do i have to root the phone to do that ?
Thank you
Related
Hi Guys, as subject really! Is it possible to get the phone in a "Google" state to pull down updates, obviously meaning the impending ICS one!
B
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
frutelaken said:
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
Click to expand...
Click to collapse
Hey mate, thankyou for helping. I've not actually received it yet, bought one off ebay and I am just pre-empting - If you flash stock does the root and unlocked bootloader become standard again??
(I'm upgrading from an old Galaxy 3, so am reasonably familiar with flashing, but want a simple life now and am going stock Google )
B
Nope, flashing a stock image will not affect your bootloader being unlocked. You'll have to run the "fastboot oem lock" command to lock the bootloader again. Check one of the turorials here
Greetz
//edit: Actually, I'm suddenly not sure of this. Sunday evenings' got me confused. Please wait for someone else to verify.
Thankyou I'll have a look round
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
n00bfuscator said:
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
Click to expand...
Click to collapse
That's normal, the OTA's reset the permissions on key folders, effectively SU looses it's execute permissions, removing root. What i do now is download the OTA to the SD card, apply it, re-apply the SU.zip to keep root, modify the restore-recovery script so i can keep CWM, then reboot.
I'm not sure how it's going to go with ICS, but we shall see.
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Check out this thread over in the dev section.
http://forum.xda-developers.com/showthread.php?t=2046439
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Frunple said:
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Click to expand...
Click to collapse
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Knightvision said:
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Click to expand...
Click to collapse
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
I can confirm that this method works. I used Voodoo to keep my root and then answered yes to allowing CWM to install the unsigned .zip and answered yes to keeping root. I then got the dreaded Verizon warning triangle and was prepared to Odin back to Stock and start over. Just by chance I went into download mode and it allowed me boot my Rom. Once in, I checked EZ-unlock and it said I was unlocked, so I went ahead and locked and then unlocked and all was good! Hope this helps saves someone else some hassle.
Real_JESRadio said:
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
Click to expand...
Click to collapse
man I tried this but it didnt work rootkeeper says its rooted but no root access the super user app is there...could i have done something wrong?? do i have do something after i upgrade to get to work?? thanx
BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
It's fixed now. The CMW recovery mode wasn't working for some reason. Whatever broke ROM Manager did so by breaking CMW Recovery. I blame myself for stupidly trying to run a backup like that. Anyway, all I could get was the triangle screen and it would only reboot to that or the CMW that wasn't working. Ended up putting it in Odin mode and reflashing with one of the no-wipe leaks. Works fine now. And VZW says I am up to date.
Will get around to rerooting/unlocking again later today. And smacking myself for getting into this mess.
Good to learn from mistakes that are not fatal. Good to have LOTS of resources to figure out how to bail it out too!
Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.
abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172
If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update
abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.
iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.
I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261
The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.
Can I have locked boot loader and be able to flash a custom ROM? It would need to be signed by who, Google, LG?
MAXGEN said:
Can I have locked boot loader and be able to flash a custom ROM? It would need to be signed by who, Google, LG?
Click to expand...
Click to collapse
Sure just send it to Google and haven them rebuild and sign it as a factory image (just kidding off course). No, that`s off course not possible.
-Edit- Read the first 4-5 threads in this section before you do anything
MAXGEN said:
Can I have locked boot loader and be able to flash a custom ROM? It would need to be signed by who, Google, LG?
Click to expand...
Click to collapse
With a locked bootloader, you cannot flash anything using fastboot.
However, if you unlocked bootloader, installed custom recovery, then relocked bootloader (pointless), you can still install stuff from recovery.
But fastboot cannot be used to flash anything (even stock Google factory image).
You sound like you come from a HTC (or similar) device where you would need to relock bootloader to flash a stock RUU, a Nexus is totally different than a HTC device. :good:
Edit: Be warned that unlocking the bootloader using "fastboot oem unlock" wipes EVERYTHING except the OS on the phone.
Thanks for the quick response.
How do ROM updates (ex. 4.0 to 4.1 ) get pushed from either the manufacturer like LG or Samsung or Google for there devices then? You have to unlock you phone to update? Typically on Samsung I downloaded through TouchWiz and then it restarted on its own and installed on its own without user unlocking anything.
So how do updates then get pushed? They must be signed and get around the lock boot loader some how? I guess the signed ROM is able to unlock it to install is that purpose then?
MAXGEN said:
Thanks for the quick response.
How do ROM updates (ex. 4.0 to 4.1 ) get pushed from either the manufacturer like LG or Samsung or Google for there devices then? You have to unlock you phone to update? Typically on Samsung I downloaded through TouchWiz and then it restarted on its own and installed on its own without user unlocking anything.
So how do updates then get pushed? They must be signed and get around the lock boot loader some how? I guess the signed ROM is able to unlock it to install is that purpose then?
Click to expand...
Click to collapse
For Google updates there is no need to be unlocked, you talked about flashing a custom rom. Updates get downloaded and installed automaticaly in fastboot.
MAXGEN said:
So how do updates then get pushed? They must be signed and get around the lock boot loader some how? I guess the signed ROM is able to unlock it to install is that purpose then?
Click to expand...
Click to collapse
Flashing /system has nothing to do with the bootloader. OTA updates flash to /system via stock recovery.
A locked bootloader prevents you fastboot flashing. You could unlock the bootloader, fastboot flash a custom recovery then lock the bootloader again. You would still be able to flash /system with custom roms. Bootloader doesn't prevent flashing. It just prevents fastboot flashing
Sent from my Nexus 5 using Tapatalk
rootSU said:
Flashing /system has nothing to do with the bootloader. OTA updates flash to /system via stock recovery.
A locked bootloader prevents you fastboot flashing. You could unlock the bootloader, fastboot flash a custom recovery then lock the bootloader again. You would still be able to flash /system with custom roms. Bootloader doesn't prevent flashing. It just prevents fastboot flashing
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What stops custom roms being flash through stock recovery?
What stops custom ROM be a OTA so it can be flash stock recovery?
MAXGEN said:
What stops custom roms being flash through stock recovery?
What stops custom ROM be a OTA so it can be flash stock recovery?
Click to expand...
Click to collapse
googles signature
simms22 said:
googles signature
Click to expand...
Click to collapse
BK in the house! Anyways.
Just to clear things up for me.
If I keep my stock recovery and keep boot loader lock, then I can't flash my ROM unless I have Google keys. Okay I got that but mentioned earlier that you can flash to the /system, OTA (Over the Air) package, does that have to be signed for that? What is the mechanism to flash OTA, stock recovery or something else?
Ultimately, something like CM is doing, if I make a ROM, I could make my own recovery and with my own keys and call it verified and safe and push OTA packages for updates??
Everything official is signed. Nothing unofficial can be signed. Nothing unsigned can be flashed without either a custom recovery or unlocked bootloader.
Hope this clears everything up for you.
Sent from my Nexus 5 using Tapatalk
Could you replace the
/system/etc/security/otacerts.zip
or
/META-INF/com/android/otacert file
with your own??
Lets cut to the chase. What is your ultimate aim here?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Lets cut to the chase. What is your ultimate aim here?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
LOL
Just trying to get an direction so I continue to do further research. Mostly my aim is more in depth understanding.
I want to build my own ROM and I'm starting that journey. Definitely a newbie but not a newbie to technology and programing and by no means an expert. Just a senior college student that with enough information to be "dangerous".
I would like to have ROM that doesn't need to have unlock boot loader or have custom recovery? Is that possible? i feel a lot ppl I meet don't like to use Custom ROMs b/c of these hurdles. I guess I would have to have root access to change out the CERTS either way.
You can't even flash a full official rom without unlocking the bootloader. It isn't possible on this device
Sent from my Nexus 5 using Tapatalk
MAXGEN said:
LOL
Just trying to get an direction so I continue to do further research. Mostly my aim is more in depth understanding.
I want to build my own ROM and I'm starting that journey. Definitely a newbie but not a newbie to technology and programing and by no means an expert. Just a senior college student that with enough information to be "dangerous".
I would like to have ROM that doesn't need to have unlock boot loader or have custom recovery? Is that possible? i feel a lot ppl I meet don't like to use Custom ROMs b/c of these hurdles. I guess I would have to have root access to change out the CERTS either way.
Click to expand...
Click to collapse
I think if it was possible, it would have been done already. But its not that big of a hurdle to unlock and root. Its actually a lot more easier than it seems. It usually takes about 5 minutes to do after getting all the necessary files. All you need is a general understanding and the ability to follow directions well.
You can't even flash a full official rom without unlocking the bootloader. It isn't possible on this device
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No i went right to a custom, unlock, root, custom Recovery, Custom Rom
jsgraphicart said:
I think if it was possible, it would have been done already. But its not that big of a hurdle to unlock and root. Its actually a lot more easier than it seems. It usually takes about 5 minutes to do after getting all the necessary files. All you need is a general understanding and the ability to follow directions well.
Click to expand...
Click to collapse
On Samsung pushed OTA and reboot and install...DONE.
So it is possible!
It isn't as easy as you think because more people would have it. I walk into any CS class less then 10% are rooted or Custom. Most of them probably are on iphones but that's different. My point is that you would think some what intelligent geeks would take the time to do so but they don't. IMO there are still hurdles and CM are trying to breach these inconveniences except Google doesn't like it.
MAXGEN said:
No i went right to a custom, unlock, root, custom Recovery, Custom Rom
On Samsung pushed OTA and reboot and install...DONE.
So it is possible!
It isn't as easy as you think because more people would have it. I walk into any CS class less then 10% are rooted or Custom. Most of them probably are on iphones but that's different. My point is that you would think some what intelligent geeks would take the time to do so but they don't. IMO there are still hurdles and CM are trying to breach these inconveniences except Google doesn't like it.
Click to expand...
Click to collapse
on samsung, samsung signs the roms, not google. so of course its possible for them.
simms22 said:
on samsung, samsung signs the roms, not google. so of course its possible for them.
Click to expand...
Click to collapse
So essentially you just need to replace the certs to push your own OTAs through your device. Which at some point you would need access to those CERTs so you would need root access.
MAXGEN said:
No i went right to a custom, unlock, root, custom Recovery, Custom Rom
Click to expand...
Click to collapse
I wasn't asking a question. I was telling you it is not even possible to flash official nexus 5 full rom from Google without unlocking the bootloader.
MAXGEN said:
On Samsung pushed OTA and reboot and install...DONE.
So it is possible!
Click to expand...
Click to collapse
As mentioned, because they signed the update and it matched what their rom and their recovery expected.
You cannot simply "guess" a signature. You cannot reverse engineer a signature. All you can do is remove whatever is validating the signature and this cannot be done without unlocking the bootloader
Sent from my Nexus 5 using Tapatalk
MAXGEN said:
On Samsung pushed OTA and reboot and install...DONE.
So it is possible!
It isn't as easy as you think because more people would have it. I walk into any CS class less then 10% are rooted or Custom. Most of them probably are on iphones but that's different. My point is that you would think some what intelligent geeks would take the time to do so but they don't. IMO there are still hurdles and CM are trying to breach these inconveniences except Google doesn't like it.
Click to expand...
Click to collapse
Are you talking about an OTA from Samsung or a custom ROM OTA without unlocking the phone. If its from Samsung then yeah, they have all the stuff to put into the OTA to bypass the locked bootloader. But anything like that probably has to come from the manufacturer because they are the only ones who have the "keys". I have never owned a Samsung device (other than the Galaxy Nexus but that was more Google). So if I'm just not understanding that, then I apologize. I think around XDA, everyone here just finds it easier to unlock, root and be on their way. But if you find a workaround, I'm sure people would be interested.
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
try this posted by @zachariahpope http://crackflasher.com/blur_version-9-18-94-xt926-verizon-en-us-zip-motorola-droid-razr-hd-cdma-livinginkaos/
billycar11 said:
try this posted by @zachariahpope http://crackflasher.com/blur_versio...zip-motorola-droid-razr-hd-cdma-livinginkaos/
Click to expand...
Click to collapse
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
samabuelsamid said:
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
billycar11 said:
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
Click to expand...
Click to collapse
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
samabuelsamid said:
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
Click to expand...
Click to collapse
I was reading that it rewrites your recovery. Go back into your recovery (should be a new version) and try to I stall again.
Yeah you need to install 2 times.
Did it install the recovery?
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
samabuelsamid said:
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
Click to expand...
Click to collapse
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
Thanks, I'll provide an update of how this works!
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
This all worked perfectly and I'm now rocking KitKat
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
samabuelsamid said:
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
Click to expand...
Click to collapse
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
iBolski said:
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
Click to expand...
Click to collapse
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
samabuelsamid said:
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
Click to expand...
Click to collapse
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
iBolski said:
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
Click to expand...
Click to collapse
good thing I asked first
Update: not rooted on KitKat!
samabuelsamid said:
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
Click to expand...
Click to collapse
I have the same problem, but I'm getting the error message that expects your device. What was the image that you used? I have the vanquish:4.1.2/9.8
1Q-94/56:user.
samabuelsamid said:
good thing I asked first
Update: not rooted on KitKat!
Click to expand...
Click to collapse
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
iBolski said:
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
Click to expand...
Click to collapse
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
samabuelsamid said:
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
Click to expand...
Click to collapse
you know what, color me stupid.
I've been helping so many people that when I read "no root", I interpreted it as "locked bootloader".
My bad.