New official version stock English rom for UK v2.51.1 released.
DOWNLOAD: Defy Rom v2.51.1
thanks, but where can we find the changelog of this new rom ?
Great! Will give it a try.
might try this tomorrow, although I can't see it being anything major, at the end of the day its not been push OTA as an update yet. I just tried the supposedly "no blur" firmware too and there was still loads of blur on it!
it is unrootable for the moiment.
Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.
TPGamer said:
Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.
Click to expand...
Click to collapse
i don´t know, but i have the "deblured" 2.34.1 firm rooted with z4root and with the clockwork recovery working
Thanks, have installed and its a nice improvement.
Not a giant leep but more of a polish. I must be one of the few people that likes the email client in motoblur.
i aint going anywhere near this it its not rootable then - there nothing wrong with 2.21 imo. And I like the blur email app too lol
If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?
the problem is that you can not flash any older than this and without root you can not flash custom recovery and can not restore nand backup.
if you flash older the phone wont boot.
Yep now unable get root access. Oh well
im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.
TPGamer said:
If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?
Click to expand...
Click to collapse
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working
andyirons said:
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working
Click to expand...
Click to collapse
we need another exploit for this rom atleast
jboogie3 said:
im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.
Click to expand...
Click to collapse
I´ve just flashed back from 2.34.1 to 2.21.0 with no major problem.
Looks like 2.51.1 UK comes with a secret within.
jboogie3 said:
we need another exploit for this rom atleast
Click to expand...
Click to collapse
yes, indeed
ya... moto patched it.. my devices goes offline after doing the - ./rageagainstthecage-arm5.bin using the droid2root method... if only it could stay online then we could have root
what the fnck....I just flash the 2.51 two hours ago. i've try atleast 3 method to root this ...all failure....Fnck moto.....
see what they did is baited you in with "noblur" and now your stuck without root!
Related
Thought I'd better post this before everyone flashes these sbfs and looses downgradability (is that a word?)
So as you may have worked out this process is if you have never flashed a non downgradable .sbf i.e you have never flashed 2.51 eclair or the 2.2 GB/US 2.2 froyo. If you flashed these then this won't work for you and youve lost downgrability.
Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here
Need the system.img nandroid and boot/devtree.sbf – Download here
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear
• Flash the Chinese .sbf by RSD lite
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder)
• Once restored pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done.
If you want to use the GB release then just restore the system.img from the GB release.
Enjoy and don't get locked in peoples.
Thanks to adlx whom I enjoyed working with to figure this out - team effort! +as always Sorensiim for the hosting!
I don't think you actually need to flash anything other than boot/devtree.
I tried TMO with uk2.51 and it was just fine.
And if someone followed your post exactly as it is now. Chances are they'd
get their phone bricked (since many are already on 2.51).
Easy to fix for sure, but since it is most likely meant for less experienced
users, we really don't want that, right?
BTW
Thanks for writing it up.
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
EDIT: Credit goes to adlx, as it was his file (mis-remembered...should have known better from the file name though). Using Higgsy's instructions and links and adlx's update, I now have a working working US 3.42 with the Motoblur setup bypassed. Thanks to all those who made that possible.
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
No you can't. Nandroid backup and/or SBF won't do anything on that front.
As I am on the UK sbf, this will not be of much use to me. Thankfully, I have no issues with that sbf, so I do not need this.
That said, thank you from those who do.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
what do you mean by "on that front"?
means that fix package consists some fundamental codes that had thoroughly change the hardware control? and nandroid backup as well as SBF could not overwrite that part?
Forgot to put in the post this is if you have not flashed a non downgradable .sbf before, although I would have thought people would be able to work that out by the nature of the thread.
This will work and will fix you cam flash if you are coming from 2.21+2.35 Eclair ROMs or 2.2 Chinese ROM where you haven't flashed a non downgradable .sbf
Higgsy said:
If you want to use the GB release then just restore the system.img from the GB release.
Click to expand...
Click to collapse
Can you provide a link to that image?
Raccroc said:
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I never posted that! and I never used that fix! On the US 3.4.2 you can't skip setup, on the GB 3.4.2 you can skip set up.
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
If you never installed a non downgradable sbf as per the updated op then yes.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Raccroc said:
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I think I did post this Skip_Blur_adlx-signed, as I'm adlx lol (although I'm registred here as adlxdum). And yes, it has to be flashed RIEGHT AFTER restoring the nandroid, as I stated. (I can't find the post...)
EDIT: was http://forum.xda-developers.com/showpost.php?p=10930470&postcount=149
Thanks mate, my DEFY is perfect now.
Muznyu said:
Thanks mate, my DEFY is perfect now.
Click to expand...
Click to collapse
Whoop!!!!!!!!!!!!!!!!!!!!!!
Higgsy said:
If you never installed a non downgradable sbf as per the updated op then yes.
Click to expand...
Click to collapse
too bad that you didn't mention this when the post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
conradlyn said:
too bad that you didn't mention this when post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
Click to expand...
Click to collapse
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Higgsy said:
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Click to expand...
Click to collapse
i also tried to hold on to this rule even before i bought my defy, but just can't reject the temptation of new ROMs...
you couldn't imagine how much i hate myself now, damn!
i could only pray for a real fix on the flash light by great guys like you, Higgsy
Higgsy said:
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Click to expand...
Click to collapse
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
racca said:
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
Click to expand...
Click to collapse
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Higgsy said:
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Click to expand...
Click to collapse
man, it is astonishing to see that it does fix, it seems that the green light indeed could be fix. but how?
is it only can be done by your operation procedure, or some independent files could be ported and flashed to fix?
Thanks a lot Higgsy. I'll try your turorial. Could I translate your topic to put it on a French forum ? (i'll put a link to the original thread)
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
how is it? faster than 2.1?
Oh yeah. More bloatware, but that's easy to remove. Internet speed is faster. Phone is more responsive. Nice to have the Hotspot feature now. Overall a worthy upgrade. Now to wait for 2.3
can i use this update for my finland rom 3.42? or this is just for TMo version?
runeblade said:
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
Click to expand...
Click to collapse
Would you happen to have original t-mobile 2.1 in sbf format?
Unfortunately no-one has one for the US. I'm guessing you updated to the leaked version? The good news is that if my suspicion is correct a nandroid backup of this should play fine with the updated firmware. If you look at the difference its minor. 34.4.9 vs 34.4.4. I have not yet had the time to make one yet. I'll try to do so tonight.
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
nanek921 said:
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
Click to expand...
Click to collapse
Its an update zip file signed by company so you should enter stock recovery by power+vol down and then select update from zip.
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
no clue said:
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Click to expand...
Click to collapse
Beach_Head said:
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
Click to expand...
Click to collapse
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
The leaked T-Mobile SBF was fast too.
But yeah, an official one would be better.
If the Nandroid method doesn't work, I hope someone posts an SBF soon...
no clue said:
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
Click to expand...
Click to collapse
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
No worries!
Is there any way to edit the build.prop file so that I can get the update to work?
runeblade said:
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
Click to expand...
Click to collapse
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
I have the string. I'm just wondering if it would work if I do edit it...
Where do I locate logwrapper?
runeblade said:
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
Click to expand...
Click to collapse
I just loaded this update.zip on my fiance's Defy...didn't wipe data or cache, it's booting right now....stuck at the T-Mobile "Stick Together" screen, waiting for the initial long boot
EDIT: Booted, running 2.2.1 now! So far so good, it's a little slow but it would be while it catches up. I have an Atrix and it's almost the identical interface.
can you make a sbf file of entire build?
Nandriod back up please! im dying for it
zencoran said:
Nandriod back up please! im dying for it
Click to expand...
Click to collapse
just flash the update.zip...why bother with a nandroid?
I bought my S3 used and it was already unlocked but from what I can tell still had the stock ROM (base version says it is I535VRLF2 but DEVICE STATUS says it is modified). When it powers up, I do not get a CWM or TWMP screen -- it goes directly to the normal startup so I am not sure what the previous owner loaded/did. I do not see any folders in the root folder (using ES FIle Explorer) for CWM and nothing in DATA/BACKUP (EDIT: just saw build number is VRALG7)...
Today I got a notice about an OTA upgrade (to HE) and got help on how to freeze it (as I did not want to lose root and all the customization I did to some files) but now I am wondering what changes were made from F2 to HE. I did find a post that talks about the HE upgrade.
Was F2 the previous OTA for the S3, or did my phone miss other OTAs? And if so, I am missing out on some important changes where I should let the OTA happen and then go and unlock the phone again? I read a number of threads about 'the new radio' which I assume is software to improve the phone or WIFI. Am I missing out?
Thanks
Frank
Michigan
I don't think you are missing out on anything to be honest. I did update mine and reroot without any issues, but can't really tell a difference. I would still do it so I can have the latest update on my phone since this one doesn't lock anything that we can't get back into.
Sent from my SCH-I535 using xda premium
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
sfobrien said:
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
Click to expand...
Click to collapse
Thanks for the reply. Will that break either my root or unlock (actually, I am not sure what state this phone is at since I did not do it -- I do find SuperSU in APPS, and have granted SuperUser to programs like Titanium Pro but there is nothing for CWM or other ROM managers...)?
Frank
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
sfobrien said:
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
Click to expand...
Click to collapse
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
FMinMI said:
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
Click to expand...
Click to collapse
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
andimanium said:
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
Click to expand...
Click to collapse
The only way to get stock HE currently is OTA.
sfobrien said:
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
Click to expand...
Click to collapse
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
FMinMI said:
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
Click to expand...
Click to collapse
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
Thanks forgot about GooManager.
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Click to expand...
Click to collapse
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
FMinMI said:
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
Click to expand...
Click to collapse
It is personal choice. I have not had any problems with it and have been running since device was released for pre-order. I run whatever recovery seems to be most stable for the device. CWM for Tbolt. Amon Ra for Rezound. And now TWRP for S3. Have seen more bricks and failed flashes contributed to CWM so I stick with TWRP.
help
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
FMinMI said:
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
Click to expand...
Click to collapse
The OTA installed with a custom recovery installed? Interesting. Usually OTA's fail if anything but stock recovery is installed. I only lost root but restored root with OTA Rootkeeper with stock recovery. Good to know that custom recovery can be installed and still get OTAs!
masonjb said:
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
Boot loader is locked.
Click to expand...
Click to collapse
prdog1 said:
masonjb said:
Boot loader is locked.
Click to expand...
Click to collapse
OK, I used EZ Unlock 1.2 and it said "unlocked" is there a way to know for sure before flashing if it is unlocked?
Thanks!
Click to expand...
Click to collapse
Just wondering if anyone has any insight on SU6-7.7 on the Droid line? Whether or not anyone know or hear anything about downgrading to a different SU version? I have the firmware file for the latest SU6-7.7 in case anyone wants it.
https://drive.google.com/open?id=0B7hPMTc_G5VPMFVqZmdMSXJEbjA
It would be nice if Motorola/Lenovo would let us do what we want with a phone they no longer "support".
Thanks, I was looking for this.
RichardCA said:
Thanks, I was looking for this.
Click to expand...
Click to collapse
Sure thing! Let me know if you need anything else!
SalmanJohnson2011 said:
Sure thing! Let me know if you need anything else!
Click to expand...
Click to collapse
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
RichardCA said:
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
Click to expand...
Click to collapse
I believe that you can replace the stock boot logo with an unlocked or locked bootloader. There are a quite a few logos to choose from. When you pick one, you fastboot the image.
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
Not sure at the moment. XD I'll reply back to this post or PM you if I do. Thanks again! If you have any more info, please let me know!
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
When you flashed it to your mini/ultra, where you on SU6-7.7?
SalmanJohnson2011 said:
When you flashed it to your mini/ultra, where you on SU6-7.7?
Click to expand...
Click to collapse
I jumped around a lot. I was playing with marshmallow and lollipop builds and needed to revert back. But I was on the Motorola stock SU4.21 when I flashed it.
I used the process on this page, and got zero errors:
http://forum.xda-developers.com/showthread.php?t=2580060
Help please!!!
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
edgar1994 said:
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
Click to expand...
Click to collapse
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
ashal said:
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
Click to expand...
Click to collapse
Nope. I've tried and it doesn't work.
SalmanJohnson2011 said:
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Click to expand...
Click to collapse
Man this really sucks i hope someone finds a way around this :crying:
edgar1994 said:
Man this really sucks i hope someone finds a way around this :crying:
Click to expand...
Click to collapse
I Agreed dude. I'm with you! I don't know why I keep getting Verizon phones. XD Regardless of what I learned. Haha
SalmanJohnson2011 said:
Nope. I've tried and it doesn't work.
Click to expand...
Click to collapse
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
ashal said:
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
Click to expand...
Click to collapse
For me, I tried going down one update at a time and it still doesn't work.
it says devoloper phones only
can I flash to my ultra even tho its not a dev phone??
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
root successful
Davey126 said:
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
Click to expand...
Click to collapse
Dear i have successfully rooted mine droid mini su6-7.7 with kingo root (not global) v3.4 successfully now i have superuser app in system directory
---------- Post added at 05:42 AM ---------- Previous post was at 05:20 AM ----------
Dear friends i have successfully root mini droid mini su6-7.7 with kingo root v3.4 (not kingo root global). actually i was trying to flash su4.21 over su6-7.7 with RSD lite v6.1 but failed with max get var and after that tried to flash with RSD lite 5.1 again failed without any error. after all of there method i thought of giving a try to kingo root. i downloaded 2 apps kingo root globalv4.9.7 and kingo root v3.4, kingo root global failed to root but.... kingo root v3.4 succeeded to roo. now i have superuser app in system driectory.
but problem is that after removing system app (amazon) when i restarted the phone all the apps came back and superuser app gone. i don't know why so my request to look into this method .
i have tested this method and worked 100% and i have no intention of making fun of me. i have both the apps but don't know how to upload here
Thanks
Hi. I'm finally can root my SM-G920R6. I use the KingRoot.apk the v4.80 and root the phone. But it's not full root. Them I use the SuperSuMe.exe on my PC to remove all the KingRoot app and install the official SuperSu.apk The program install it's self. And now we can install the correct binary and reboot the device and don't lose root... ohh and my Knox still 0x0... =) XD:laugh: :victory: :highfive:
Links:
●KingRoot v4.80
●SuperSuMe. for PC
Sincerely I don't know if full root or not. But for me is working. And other things I don't know is full knox disabled. The SuperSuMe block the knox in one of the process but I don't know if is disabled at all or not.
I wish this can't help all the SM-G920R6 user. And don't want to avoid the knox warranty.
The only thing you can see is every time you BootUp your phone it say Custom.
The next thing I'm going to do is make a full backup with FlashFire app because mi firmware not appear in SamMoblie. If one Dev can make something with this backup for make custom roms or something good for this devices model.
my phone info:
Android Version : 5.0.2
Baseband : G920R6WWU1AOE4
Build Number : LRX22G.G920R6WWU1AOE4
Hardware Version : G920R6.02
I'm not a good English speaker so I apologize my errors..
P.S.
Sorry I'm not a Dev. this is my first Thread and I do this for helping.
This is a little off topic for the op but I really need help right now.. I rooted with CF autoroot for G920F no problem then installed TWRP 3.0.2-1 zeroflteusc also built for G920F model and in the process of trying to find a better rom as soon as I had a custom recovery, me (being a dumba**) accidentally wiped my internal storage to do a clean flash of a rom therefore deleting the only backup I had. I've only been able to find the factory binary for this device which I flashed but it had literally nothing exept for basic testing software and a simple ui to run it. It was also stuck on Android 5.0.2 but I found a compatible rom with AllianceROM v1 with update v2 flashed for the G920F but I can't find any way to update past 5.0.2!! I've been trying to find a way to update somehow for weeks but nothing is compatible with my device and I'm stuck. Would someone that has my model running on Android 5.1.1 or 6.0/.1 please install the TWRP I mentioned before and make a backup of the system, modem, efs, and boot and post it online or send it to me it would be a lot of help.
Reasons I hate you I guess ?
You are a real piece of **** and a cancer to those with A ACTUAL SAMSUNG-SMG920V.
I don't even know why you posted this here you don't even have a SM G920R6.
Seriously you just made me give up hope once again on getting root on my SAMSUNG-SMG920 on android 6.0.1 :crying:
Sincerely yours ( Another piece of **** with this **** tastic phone that dies in 3 hours and you can do jack **** with)
P.s. It also dies in 3 hours no matter what I install on it no matter on many resource manager apps I use, it just ****ing dies.
P.s.s. Sorry for swearing so much...
hoppits said:
You are a real piece of **** and a cancer to those with A ACTUAL SAMSUNG-SMG920V.
I don't even know why you posted this here you don't even have a SM G920R6.
Seriously you just made me give up hope once again on getting root on my SAMSUNG-SMG920 on android 6.0.1 :crying:
Sincerely yours ( Another piece of **** with this **** tastic phone that dies in 3 hours and you can do jack **** with)
P.s. It also dies in 3 hours no matter what I install on it no matter on many resource manager apps I use, it just ****ing dies.
P.s.s. Sorry for swearing so much...
Click to expand...
Click to collapse
Because my device is G920R6 originally and i want it back the 920F rom is barely compatible with my device as is and i want a stable rom made for my build and also to enlighten others of how i rooted this phone and what custom recovery is working for me. Even on 5.0.2 and an unstable rom my battery lasts 6+ hours of constant use so root is working fine for me.
So much hate.
yeah i see now this model phone is the ugly duck....
But some one have the factory firmware of this model flashable with odin. Thanks a lot.
Casper1619 said:
This is a little off topic for the op but I really need help right now.. I rooted with CF autoroot for G920F no problem then installed TWRP 3.0.2-1 zeroflteusc also built for G920F model and in the process of trying to find a better rom as soon as I had a custom recovery, me (being a dumba**) accidentally wiped my internal storage to do a clean flash of a rom therefore deleting the only backup I had. I've only been able to find the factory binary for this device which I flashed but it had literally nothing exept for basic testing software and a simple ui to run it. It was also stuck on Android 5.0.2 but I found a compatible rom with AllianceROM v1 with update v2 flashed for the G920F but I can't find any way to update past 5.0.2!! I've been trying to find a way to update somehow for weeks but nothing is compatible with my device and I'm stuck. Would someone that has my model running on Android 5.1.1 or 6.0/.1 please install the TWRP I mentioned before and make a backup of the system, modem, efs, and boot and post it online or send it to me it would be a lot of help.
Click to expand...
Click to collapse
Hi. i found a factory SM-G920R6 Android 6.0.1 frimware... but this android version I'm rooted with the same cf auto root you used .
And I don't know remember were i downloaded the firmware.. But later I try to uploaded.
M3RS3 said:
Hi. i found a factory SM-G920R6 Android 6.0.1 frimware... but this android version I'm rooted with the same cf auto root you used .
And I don't know remember were i downloaded the firmware.. But later I try to uploaded.
Click to expand...
Click to collapse
Could you install the twrp recovery I mentioned and make a backup of the system and boot and post that?
Casper1619 said:
Could you install the twrp recovery I mentioned and make a backup of the system and boot and post that?
Click to expand...
Click to collapse
yeap.. but when I install the recovery the phone gave a glitch.. its flipping the touch response inverted.. and the only fix is with root. and use the app. phone info.apk for Samsung and use the secret code with root because it is blocked on the dialer.
but i have the backup for the new firmware. not the android 5.0.2
M3RS3 said:
yeap.. but when I install the recovery the phone gave a glitch.. its flipping the touch response inverted.. and the only fix is with root. and use the app. phone info.apk for Samsung and use the secret code with root because it is blocked on the dialer.
but i have the backup for the new firmware. not the android 5.0.2
Click to expand...
Click to collapse
That's exectly what I need I'm stuck on 5.0.2 and I want to upgrade back to 6.0.1 it's mainly the bootloader I need because no other marshmallow bootloaders work for this phone and the one I have is only for 5.0.2
Casper1619 said:
That's exectly what I need I'm stuck on 5.0.2 and I want to upgrade back to 6.0.1 it's mainly the bootloader I need because no other marshmallow bootloaders work for this phone and the one I have is only for 5.0.2
Click to expand...
Click to collapse
But i have the stock firmware flashable with odin. you have my same phone. SM-G920R6?
M3RS3 said:
But i have the stock firmware flashable with odin. you have my same phone. SM-G920R6?
Click to expand...
Click to collapse
Yeah if you could send it to me that would be awesome
Casper1619 said:
Yeah if you could send it to me that would be awesome
Click to expand...
Click to collapse
you can download send anywhere app in playstore and i cand send directly to you.
.....
ohhh let me check if i haved in the phone because i give my pc to one cousin to make some homework. and i dont haved right now.
M3RS3 said:
you can download send anywhere app in playstore and i cand send directly to you.
Click to expand...
Click to collapse
Alright I've got work then I'll be back
Casper1619 said:
Alright I've got it ready whenever you are
Click to expand...
Click to collapse
Give me some minute to go to my cousin house.. is near of my house to get the file and copy on my pendrive..
Casper1619
Sorry i go to uplode the two file. the BACKUP and the Stock Firmware 6.0.1 in MEGA and then i post the two links.. I promes... because the internet it come extremely slow... when i uploded the two file i posted ok...
M3RS3 said:
Sorry i go to uplode the two file. the BACKUP and the Stock Firmware 6.0.1 in MEGA and then i post the two links.. I promes... because the internet it come extremely slow... when i uploded the two file i posted ok...
Click to expand...
Click to collapse
Okay how long do you think it'll be?
Casper1619 said:
Okay how long do you think it'll be?
Click to expand...
Click to collapse
i don't know maybe for tomorrow.. have a good night.:good:
M3RS3 said:
i don't know maybe for tomorrow.. have a good night.:good:
Click to expand...
Click to collapse
Okay thanks you too