Related
I am receiving my new N1 Fri. Have been reading about rooting and all, does a new phone come with all the settings to the factory resets? Are there differences between my unlocked AT&T phone and others? If I choose to upgrade to new ROM's are my steps different? Been trying to figure it all out but unsure. Thanks
yes it comes with factory settings if its brand new.
upgrading to new roms won't be any different if you're on AT&T.
Link below is for nexus one in general, carrier doesn't matter.
http://forum.xda-developers.com/showthread.php?t=688000
Makes sense. If I do decide to install a rom I would only have to load the file onto the sd card and install? Are the advantages of the rom's better performance or features?Been spending a lot of time trying to get educated but too many ques.
erikclaw said:
Makes sense. If I do decide to install a rom I would only have to load the file onto the sd card and install? Are the advantages of the rom's better performance or features?Been spending a lot of time trying to get educated but too many ques.
Click to expand...
Click to collapse
better features and access for more customization.
mrandroid said:
Link below is for nexus one in general, carrier doesn't matter.
Saw your post after I replied. So after reading, I wouldn't have to root for the Froyo install? Just the steps you listed? Is the reason for rooting going from one rom to a newer or different one? Or do others have to do that because their phones are locked? Mine is unlocked cause with AT&T.
Click to expand...
Click to collapse
erikclaw said:
mrandroid said:
Link below is for nexus one in general, carrier doesn't matter.
Saw your post after I replied. So after reading, I wouldn't have to root for the Froyo install? Just the steps you listed? Is the reason for rooting going from one rom to a newer or different one? Or do others have to do that because their phones are locked? Mine is unlocked cause with AT&T.
Click to expand...
Click to collapse
all nexus ones are unlocked lol. and yes you do not need root for froyo and there are ways to downgrade to an official 2.1. an unlocked bootloader allows you to run unofficial roms cooked up by people and lets you flash anything you want.
Click to expand...
Click to collapse
mrandroid said:
Link below is for nexus one in general, carrier doesn't matter.
Saw your post after I replied. So after reading, I wouldn't have to root for the Froyo install? Just the steps you listed? Is the reason for rooting going from one rom to a newer or different one? Or do others have to do that because their phones are locked? Mine is unlocked cause with AT&T.
Click to expand...
Click to collapse
you don't need root for froyo but you need the correct zip to flash.
theres one for people with root access and the other is signed by google.
you bought an unlocked phone but your bootloader is still locked.
just make sure you follow the 2 prerequisites first, then follow the instructions on that post. you'll be good to go.
dudebro said:
you don't need root for froyo but you need the correct zip to flash.
theres one for people with root access and the other is signed by google.
you bought an unlocked phone but your bootloader is still locked.[
So I would have to root to make my phone able to run Froyo? Correcting the zip to flash is making it able to run flash? I know it is elementary but not sinking in.
Click to expand...
Click to collapse
dudebro said:
you don't need root for froyo but you need the correct zip to flash.
theres one for people with root access and the other is signed by google.
you bought an unlocked phone but your bootloader is still locked.[
So I would have to root to make my phone able to run Froyo? Correcting the zip to flash is making it able to run flash? I know it is elementary but not sinking in.
Click to expand...
Click to collapse
no, you do not need root to run froyo.
miketlo said:
erikclaw said:
all nexus ones are unlocked lol. and yes you do not need root for froyo and there are ways to downgrade to an official 2.1. an unlocked bootloader allows you to run unofficial roms cooked up by people and lets you flash anything you want.
Click to expand...
Click to collapse
ok, thanks for the info.
Click to expand...
Click to collapse
So basically, Nexus reads and loads roms etc like a computer? For new programs etc sometimes you need to upgrade driver ie zip to flash
dudebro said:
you don't need root for froyo but you need the correct zip to flash.
theres one for people with root access and the other is signed by google.
you bought an unlocked phone but your bootloader is still locked.
Click to expand...
Click to collapse
since I don't have to root then I have root access?
erikclaw said:
since I don't have to root then I have root access?
Click to expand...
Click to collapse
nope... I must be confusing you.
- you do not have root access after flashing froyo
- no you don't need root to flash it
- follow the steps in the thread and you will be fine
You do not have to root to run froyo. There are two flavors of Froyo floating around the net. They are the same OS version, but each can be used on a different setup.
One is a .zip signed by Google that can be flashed on an untouched/stock Nexus One, i.e. a locked bootloader. It's just a simple option selection in the bootloader to enter recovery mode. Recovery is where the updates are flashed.
The other version of Froyo that is out there is one that has root enabled, which is not signed by Google, and can only be flashed using a bootloader that is unlocked. Remember everything is flashed in recovery mode. By unlocking the bootloader you are able to replace the default recovery (which only allows the installation of signed files) with a custom one. The custom recovery allows you to flash unsigned files, many of which have root access.
In short, unlocking a bootloader does not give you root. It simply provides a mechanism by which you can flash an update that has root.
The signed file is only available for the T-Mobile 3G frequency phone thus far. It can still be flashed on an ATT one, but additional steps are required.
I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?
AGISCI said:
I just got the 4.4.2 update from claro in chile. But I have not installed it yet. My phone is on 4.2.2 at the moment. The bootloader is unlocked. It is rooted using rockmymoto. What I want to know is what do I need to do to get it ready for the 4.4.2 upgrade? I assume I need to unroot it? Also I have lucky patcher installed and I odexed my system, will this be a problem? Will I be able to get root in 4.4.2?
Click to expand...
Click to collapse
There are threads on this in the general folder as well as this folder.
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Do you have the 4.2.2 post camera update installed?
Cozume said:
There are threads on this in the general folder as well as this folder.
Click to expand...
Click to collapse
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Cozume said:
What I don't understand is why you had to root using rockmymoto if your bootloader is unlocked? Why didn't you just flash a custom recovery like TWRP and install SuperSU to root?
Click to expand...
Click to collapse
Because I rooted it a month before I unlocked the bootloader.
I still currently have stock recovery though.
Cozume said:
Do you have the 4.2.2 post camera update installed?
Click to expand...
Click to collapse
As far as the post camera update, not sure. My camera version is 3.1.41.2.
AGISCI said:
I have read various topics in both of the forums on it. But I wanted to be 100% sure of what path I need to follow to be sure I don't brick my phone. 1 thing that had me worried is that I odexed my system with lucky patcher... does this mean I am going to have to flash my firmware back to stock before I can do this?
Click to expand...
Click to collapse
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.
Cozume said:
That is certainly the safest way to go from all I have read as any system mods could potentially cause a problem. The problem that another poster here had is that the only firmware that is posted for the Claro Chile is the precamera update. He was looking for the postcamera firmware.
http://forum.xda-developers.com/showthread.php?t=2649806
And no one could help him find it. I don't think you can take the OTA if you are on the precamera firmware. Perhaps you can PM the OP in that link and see if he is knowledgeable about Claro chile firmware.
Click to expand...
Click to collapse
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?
AGISCI said:
How can I tell if I am on the pre cam or post cam? Also is there a link that talks about what teh pre cam and post cam does or changed?
Click to expand...
Click to collapse
Go to Settings->About Phone->System Version. What does it say?
139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk
AGISCI said:
139.12.35.ghost_row.AmericaMovil.en.CL
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
From the version numbers here:
http://sbf.droid-developers.org/phone.php?device=0
As best I can tell 139.12.35 is the post camera update. The problem is that no one has a copy of the stock firmware posted anywhere that anyone can find.
If that's the case flashing this firmware will not brick me then correct?
Sent from my Nexus 7 using Tapatalk
You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.
Steve-x said:
You say you rooted the phone a month before you unlocked the bootloader. If this is the case then your phone should have been wiped clean as unlocking the bootloader performs a full wipe of the phone.
So something does not add up/make sense.
Click to expand...
Click to collapse
I rooted it twice actually. After I unlocked the bootloader it was erased just like you said, and I rooted again using the same method from the first time.
AGISCI said:
If that's the case flashing this firmware will not brick me then correct?
Click to expand...
Click to collapse
Which firmware?
This is from dray_jr on the thread in the Moto X General forum:
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
http://forum.xda-developers.com/showthread.php?t=2635366&highlight=brick&page=5
You are in quite a unique situation here actually... since there is no stock image that you can go back to. If there was a 4.4 SBF I would have suggested to flash then take the 4.4.2 update. However, it seems as if there was no 4.4 roll out/update for your carrier at all. So this 4.4.2 carrier update would be more than a simple patch from 4.4 to 4.4.2, it would probably end up removing root since you are going from JB to KK.
Your best bet if you want it now is to do the following...
I AM NOT RESPONSIBLE FOR YOUR ACTIONS OR BRICKING YOUR DEVICE
1) Did you make a backup before you messed with anything in the system? If you didn't, then you have to go through the manual process of making sure that it is as clean as a normal stock image.
2) Do you have the original recovery? If not, find a recovery file for your carrier and flash that.
3) Attempt to flash the OTA in the standard recovery.
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.
mastarifla said:
But honestly, the safest thing to do is to wait until your 4.4.2 SBF is released, that way you can flash it in RSD Lite, preventing a brick as much as possible.
Click to expand...
Click to collapse
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.
I guess I will have to wait then. I can't afford to brick my phone. I captured the update and pulled it with adb so if anyone needs it I will be able to upload it.
Sent from my Nexus 7 using Tapatalk
Cozume said:
Who releases the sbf? Motorola? Because it looks like the problem is that no one can find the sbf for the 4.2.2 postcamera update for their carrier.
Click to expand...
Click to collapse
Skrilax_CZ maintains the website where the SBF's are stored. Motorola only releases the Developer Edition images to the public, as far as I know. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he has a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite (or using manual flash, if you like to live dangerously )
mastarifla said:
Skrilax_CZ maintains the website where the SBF's are stored, as far as I know, Motorola only releases the Dev edition images to the public. So I believe that this website hosts either his own custom made zips, or he has someone supplying him with insider Moto images (or he works there?).
Personally I think he a tool to automate this process once he has the firmware loaded onto the phone (if he doesn't have the images already), basically he is adb copying files from the dev partition of his phone and compiling a MD5 hash for each file, then zipping it all up in a nice package to flash with the insider Moto tool RSD Lite.
Click to expand...
Click to collapse
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
mastarifla said:
Motorola only releases the Developer Edition images to the public, as far as I know.
Click to expand...
Click to collapse
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?
Cozume said:
Thanks! So if you know someone with a stock phone who has never modded or rooted, theoretically you could pull the files from the dev partition of their phone? The trick is getting it into a package that works with RSD Lite?
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
So those of us with Dev Eds should stick to flashing the factory images we get from Motorola directly?
Click to expand...
Click to collapse
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Oh and before I forget, hitting the thanks button works too by the way
mastarifla said:
Theoretically yes, but in practice it is much harder. Every manufacturer stores their particular data in different partitions on the phone. You have to manually look through the bin files (with a hex editor) in order to determine which are the correct ones. This is even more difficult because most of the information is encrypted. So unless you have insider knowledge or want to compare values in a hex editor, I would strongly suggest you stay away from attempting to make your own files, it can lead to very easy bricks.
Click to expand...
Click to collapse
no, I would never try it; I am just trying to understand what the differences are between the various ways for me to brick my device, lol!
mastarifla said:
I have a XT1053 Unlocked GSM phone (T-Mobile), and the SBF T-Mobile firmwares are the only thing I am going to be flashing, don't flash other regions firmware unless you are certain that it works. IE. let everyone else try it and potentially brick their phone before you end up doing the same thing.
Click to expand...
Click to collapse
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
mastarifla said:
Oh and before I forget, hitting the thanks button works too by the way
Click to expand...
Click to collapse
I know I tried but they limit you to 8 thanks a day and I already used mine up for today! I will come back tomorrow and hit the button, promise. I am very good about that. So good that I use up all my thanks quickly. So odd they do that here, but they do.
Cozume said:
but if I have a Dev Ed, shouldn't I be flashing the factory images I received from Motorola?
Click to expand...
Click to collapse
Yes you should, however it is widely known that the T-Mobile version and the Developer Edition have the exact same hardware/firmware (XT1053), actually I think they may have the exact same software build as well, though I am not sure on that one... if they receive the same OTA update that the T-Mobile version receives, that leads me to believe its the same ROM.
I want restore my Moto X back to out of the box state.
I am currently rooted but I still have stock recovery, no twrp installed.
Mine is the UK GB firmware & I would like to flash it back the RSD Motorola tool but I am having trouble finding the Firmware.
I'm not sure if this would the correct firmware to use... http://sbf.droid-developers.org/phone.php?device=37
Any ideas?
Ta
@home said:
I want restore my Moto X back to out of the box state.
I am currently rooted but I still have stock recovery, no twrp installed.
Mine is the UK GB firmware & I would like to flash it back the RSD Motorola tool but I am having trouble finding the Firmware.
I'm not sure if this would the correct firmware to use... http://sbf.droid-developers.org/phone.php?device=37
Any ideas?
Ta
Click to expand...
Click to collapse
Anyone?
Ta
you need the xt1092 version: http://www.filefactory.com/folder/dd05c058d3ff8dbe
godutch said:
you need the xt1092 version: http://www.filefactory.com/folder/dd05c058d3ff8dbe
Click to expand...
Click to collapse
Is this for the UK version?
My firmware 21.21.42.victara_retgb.retball.en.GB retgb
@home said:
Is this for the UK version?
My firmware 21.21.42.victara_retgb.retball.en.GB retgb
Click to expand...
Click to collapse
Not to sure but looking at the same it's for all european retail versions
edit: I see 2 more 1092 files have been added, I think I would try reteuall= retail eu all?
godutch said:
Not to sure but looking at the same it's for all european retail versions
edit: I see 2 more 1092 files have been added, I think I would try reteuall= retail eu all?
Click to expand...
Click to collapse
Yeah that's the one I'm downloading.
Just a bit cautious cause it doesn't have the GB in the name.
Did you flash it? Did it work? Any problems?
@home said:
Yeah that's the one I'm downloading.
Just a bit cautious cause it doesn't have the GB in the name.
Click to expand...
Click to collapse
rakesh84 said:
Did you flash it? Did it work? Any problems?
Click to expand...
Click to collapse
No I didn't.
I was thinking of just unrooting with SU. I rooted with pure2014sb but I'm not sure if that's altered my stock recovery?
Like I said I haven't installed TWRP or CWM.
I rooted with the same method as you.
I will keep reading up and post in here what I end up doing.
rakesh84 said:
I rooted with the same method as you.
I will keep reading up and post in here what I end up doing.
Click to expand...
Click to collapse
Does this rooting method alter the stock recovery?
To answer my own question - NO it doesn't. I have booted in to stock recovery.
Ta
Afaik the rooting method we used didn't alter the stock recovery. Technically we didn't flash anything we booted a IMG which rooted the phone for us.
I am not sure what you mean about the Android laid on his back. I don't recall seeing that when I did it.
Did you try rooting and it didn't work?
rakesh84 said:
Afaik the rooting method we used didn't alter the stock recovery. Technically we didn't flash anything we booted a IMG which rooted the phone for us.
I am not sure what you mean about the Android laid on his back. I don't recall seeing that when I did it.
Did you try rooting and it didn't work?
Click to expand...
Click to collapse
I meant when you access recovery - the android guy laid down with red triangle - I still have stock recovery.
Having the same problem, can't get to stock recovery, just get the same icon
kylepsp said:
Having the same problem, can't get to stock recovery, just get the same icon
Click to expand...
Click to collapse
When you get to that icon.....press & hold bothe the volume up/down at the same time for about 5 sec, then pres power button while still holding the vol up/down buttons.
@home said:
When you get to that icon.....press & hold bothe the volume up/down at the same time for about 5 sec, then pres power button while still holding the vol up/down buttons.
Click to expand...
Click to collapse
is this to get to recovery? I can boot normally fine, I just need to get to recovery to use adb sideload
kylepsp said:
is this to get to recovery? I can boot normally fine, I just need to get to recovery to use adb sideload
Click to expand...
Click to collapse
Recovery Yes
@home said:
Recovery Yes
Click to expand...
Click to collapse
It just booted to fastboot after doing this. When trying to flash stock recovery using the toolkit I get an error "hab check failed for recovery"
Hi...any leak of the retgb KitKat version of the firmware? Id love to return to stock when the Lollipop OTA comes out
Sent from my retgb using XDA Free mobile app
thefunkydonkey said:
Hi...any leak of the retgb KitKat version of the firmware? Id love to return to stock when the Lollipop OTA comes out
Sent from my retgb using XDA Free mobile app
Click to expand...
Click to collapse
I've not seen a retgb rom anywhere.
I read that the Cricket Galaxy S5 (G900AZ) is a rebranded AT&T S5 (G900A). Has anyone tried ODIN flashing the stock AT&T rom on the Cricket model?
For instance, i have read people flashing the Tmobile S5 stock rom on the MetroPCS version and it works fine even though the model numbers are slightly different. It changes the phone into the Tmobile version.
spydc said:
I read that the Cricket Galaxy S5 (G900AZ) is a rebranded AT&T S5 (G900A). Has anyone tried ODIN flashing the stock AT&T rom on the Cricket model?
For instance, i have read people flashing the Tmobile S5 stock rom on the MetroPCS version and it works fine even though the model numbers are slightly different. It changes the phone into the Tmobile version.
Click to expand...
Click to collapse
Did you ever get an answer to this?
NO, but....
The Cricket S5 is indeed a rebranded AT&T model. I have both of those models including a LA G900M (TTT.) Major difference is nowhere near as much bloatware, and most importantly an unlocked bootloader. The only advantage would be upgrading to MM if you want stock, since the January update still has it on LP. You're better off trying a LA stock ROM though (I say this because they use the same custom recovery) But cutom ROM's can take you there as far as 7.1 Nougat right now.
I just recently rooted my Cricket model with CF Auto-root (klteaio), flashed the latest TWRP (klte) recovery and installed Xposed Framework (by dkcldark... wanam custom won't work.) Had a little of lag first couple of days, but I guess that's to be expected. Hope this helps in some way.
gello924 said:
The Cricket S5 is indeed a rebranded AT&T model. I have both of those models including a LA G900M (TTT.) Major difference is nowhere near as much bloatware, and most importantly an unlocked bootloader. The only advantage would be upgrading to MM if you want stock, since the January update still has it on LP. You're better off trying a LA stock ROM though (I say this because they use the same custom recovery) But cutom ROM's can take you there as far as 7.1 Nougat right now.
I just recently rooted my Cricket model with CF Auto-root (klteaio), flashed the latest TWRP (klte) recovery and installed Xposed Framework (by dkcldark... wanam custom won't work.) Had a little of lag first couple of days, but I guess that's to be expected. Hope this helps in some way.
Click to expand...
Click to collapse
Wait, it has an unlocked bootloader on the rebranded G900A?
Vesnyx said:
Wait, it has an unlocked bootloader on the rebranded G900A?
Click to expand...
Click to collapse
This gives me an idea.... What if we use flashfire to flash G900AZ firmware on the G900A (including the UNLOCKED BOOTLOADER)
Sent from my Amazon KFGIWI using XDA Labs
AptLogic said:
This gives me an idea.... What if we use flashfire to flash G900AZ firmware on the G900A (including the UNLOCKED BOOTLOADER)
Click to expand...
Click to collapse
You could always try it. I don't know exactly how well it will work.
You would have to be rooted FIRST on the G900A in order for FlashFire to work. If i remember correctly anything already on LP can't be rooted or downgraded back to KK.
---------- Post added at 11:30 PM ---------- Previous post was at 11:12 PM ----------
Y'know what would be really nice???: Seeing that android updates are only good for 2yrs on a particular model after its initial released, and the given the fact that most carries plans are only 2yrs; wouldn't it be nice if (for sake of argument in THIS thread) AT&T would release a firmware for their phones, that would unlock the bootloader and possibly SIM unlock the phone as well. I mean after 2yrs the device is paid for and quite frankly no longer belongs to them. I hate the idea of being forced to either get a new device once my plan has expired or use MY phone with the carrier its branded under. Of course it probably has everything to with them making their money from those of us who can't do without having a new device every year.
So I can pull a copy of the G900AZ engineering firmware I found, but I doubt we'll be able to flash it. What is was thinking is that we use beaups CID changer to make our device into one similar to the cricket wireless one. Since it is essentially a dev edition of our phone.
You cant just flash a unlocked bootloader to a locked bootloader phone. A specific explout must be developed to defeat the bootloader. Simply shashing over it will never work.
The G900AZ is just a rebranded version of the G900A though. I don't think there are any glaring differences like there would be from G900T to G900A. If the aboot does flash then it would be a simple unlock.
@NavSad @AptLogic
If you wanna try this, here's a link to their firmwares:
https://www.sammobile.com/firmwares/database/SM-G900AZ/
You'd most likely need to extract the correct files and be on the correct versions before flashing these.
Apparently, something similar happened with the T-Mobile Galaxy S6, where the MetroPCS firmware was flashed on the T-mobile firmware.
Vesnyx said:
The G900AZ is just a rebranded version of the G900A though. I don't think there are any glaring differences like there would be from G900T to G900A. If the aboot does flash then it would be a simple unlock.
@NavSad @AptLogic
If you wanna try this, here's a link to their firmwares:
https://www.sammobile.com/firmwares/database/SM-G900AZ/
You'd most likely need to extract the correct files and be on the correct versions before flashing these.
Apparently, something similar happened with the T-Mobile Galaxy S6, where the MetroPCS firmware was flashed on the T-mobile firmware.
Click to expand...
Click to collapse
I tried ODINing the G900AZTUU3BOG3 firmware, and it immediately returned a SECURE CHECK FAIL: aboot
I'll try using FlashFireon it tomorrow during my batch of tests.
AptLogic said:
I tried ODINing the G900AZTUU3BOG3 firmware, and it immediately returned a SECURE CHECK FAIL: aboot
I'll try using FlashFireon it tomorrow during my batch of tests.
Click to expand...
Click to collapse
Just so I can get an idea of what everyone's fuse values are, do you mind telling me what you see after RP SWREV in Download Mode.
NavSad said:
Just so I can get an idea of what everyone's fuse values are, do you mind telling me what you see after RP SWREV in Download Mode.
Click to expand...
Click to collapse
Mine are S1, T1, R1, A2, P1. I'm on Lollipop 5.0 with with ability to downgrade to NCE.
Also @AptLogic, maybe try through stock recovery, just as a precautionary measure.
P l e a s e do not try this
So I tried using FlashFire to flash the G900AZ firmware and I HARD BRICKED MY PHONE.
If anyone wants to give me advice on how to unbrick it PLEASE DO because I have to put all my development on hold indefinitely until I can unbrick it or buy a new one (which isn't likely because I don't have the cash for that right now).
AptLogic said:
So I tried using FlashFire to flash the G900AZ firmware and I HARD BRICKED MY PHONE.
If anyone wants to give me advice on how to unbrick it PLEASE DO because I have to put all my development on hold indefinitely until I can unbrick it or buy a new one (which isn't likely because I don't have the cash for that right now).
Click to expand...
Click to collapse
Try using a debrick image.
NavSad said:
Try using a debrick image.
Click to expand...
Click to collapse
I can't get the phone to boot, not even into Download Mode
AptLogic said:
I can't get the phone to boot, not even into Download Mode
Click to expand...
Click to collapse
Does it show up as qualcomm qhusb hulk when connected to your pc in device manager?
NavSad said:
Does it show up as qualcomm qhusb hulk when connected to your pc in device manager?
Click to expand...
Click to collapse
I took the battery out of the phone and hooked it up to my computer and its showing up as "RELINK HS-USB QDLoader 9008 (COM14)" in device manager
AptLogic said:
I took the battery out of the phone and hooked it up to my computer and its showing up as "RELINK HS-USB QDLoader 9008 (COM14)" in device manager
Click to expand...
Click to collapse
I would try this method:
Grab a sdcard
Grab a debrick image here:https://www.androidfilehost.com/?fid=457095661767140194
Then put the sdcard in your computer and use Win32 DiskImager to write to the sdcard. After that, put the sdcard in your phone and boot into Download Mode.
If your phone isn't fixable using this method you'd have to try JTAG.
NavSad said:
I would try this method:
Grab a sdcard
Grab a debrick image here:UPLOADING
Then put the sdcard in your computer and use Win32 DiskImager to write to the sdcard. After that, put the sdcard in your phone and boot into Download Mode.
If your phone isn't fixable using this method you'd have to try JTAG.
Click to expand...
Click to collapse
Is the debrick image just the first 200MB of the phone's data?
Hello everyone. I'm attempting to assist @arindambag recover his device from a soft brick.
If anyone with a rooted Desire 628 (2PVG) could provide a dump of their hboot or hosd, it would be greatly appreciated.
The version doesn't matter. It is only needed to generate a key file for the RUU extraction tool.
How to root htc desire 628 dual sim?
Tathyajit said:
How to root htc desire 628 dual sim?
Click to expand...
Click to collapse
It seems that some people were able to root with Kingroot on the originally released rom, but, as far as I know, there's no way to root yet after updating.
With no custom recovery (yet), root will not be possible unless another vulnerability is discovered.
CSnowRules said:
It seems that some people were able to root with Kingroot on the originally released rom, but, as far as I know, there's no way to root yet after updating.
With no custom recovery (yet), root will not be possible unless another vulnerability is discovered.
Click to expand...
Click to collapse
Then is there any process to go back to the original rom? I mean revert this update? If we flash the original stock rom before update? Then we will be able to root it with KingRoot
Tathyajit said:
Then is there any process to go back to the original rom? I mean revert this update? If we flash the original stock rom before update? Then we will be able to root it with KingRoot
Click to expand...
Click to collapse
If you can s-off, you should be able to use any RUU for your phone or change regions with a CID change, but I'm not that familiar with the HTC mediatek devices, though.
Any update brother for my case?
arindambag said:
Any update brother for my case?
Click to expand...
Click to collapse
None so far. I really need an hboot for your model. Or images, or anything really...
It is really difficult to support without the phone or images.
CSnowRules said:
None so far. I really need an hboot for your model. Or images, or anything really...
It is really difficult to support without the phone or images.
Click to expand...
Click to collapse
Since Tathyajit has the same model and also in working condition, can we extract the hboot or system image file from his phone and check? Just a thought. In that case, we need to guide Tathyajit how to do that, if required.
Without root permission,is it possible to extract hboot and system image file.
@Tathyajit: Please share your getvar info so that we can know the model and version of your phone.
arindambag said:
Since Tathyajit has the same model and also in working condition, can we extract the hboot or system image file from his phone and check? Just a thought. In that case, we need to guide Tathyajit how to do that, if required.
Without root permission,is it possible to extract hboot and system image file.
@Tathyajit: Please share your getvar info so that we can know the model and version of your phone.
Click to expand...
Click to collapse
No, root or custom recovery would be required to get an hboot image.
Still not able to restore my phone, any help please......
arindambag said:
Still not able to restore my phone, any help please......
Click to expand...
Click to collapse
Tell me if i can help in any way
Tathyajit said:
Tell me if i can help in any way
Click to expand...
Click to collapse
If you can find a way to get root on your device, I'll be able to provide instructions to extract what I need to decrypt the RUUs for all Desire 628s. Unfortunately, without root and no custom recovery available at this point, the only way to fix @arindambag's phone is via a RUU that is not available (yet).
Need help please, could able to install the RUU for version 1.17.400.1 and the phone also started successfully, but suddenly the phone went off and now it's not starting. I tried all combinations of Volume Up, Down, Power, etc. but could not able to start. Once the charger is connected, pressing the Power button shows the Battery icon once and then again the phone goes off. Pressing combinations of hard buttons, I could able to listen in my PC that connecting/disconnecting sound is coming but nothing getting displayed in the screen.
At one point of time,the HTC logo screen did come but the phone again going to the black screen.
Any suggestions would really help me.
Check this if you could find what you need
I have root via kingroot on a purchased outright medtech HTC desire 628. If you tell me how to go about getting any info that would help let me know.
Sent from my htc_v36bml_uhl using XDA Labs
Hey guys! I'm using this desire 628 and I have successfully unlocked bootloader, rooted and also flashed custom recovery (TWRP). If you need any assists.. leave a reply!?
DKrbD235 said:
Hey guys! I'm using this desire 628 and I have successfully unlocked bootloader, rooted and also flashed custom recovery (TWRP). If you need any assists.. leave a reply!?
Click to expand...
Click to collapse
Yeah man, how did you do it?
cinimod666 said:
Yeah man, how did you do it?
Click to expand...
Click to collapse
Its really simple mahn... Just download TWRP builder. Grant root access and upload your boot image. Make sure you have backed up your current boot.img . When the custom twrp recovery is ready, the app will let you know. For me, it didn't work. Then I contacted the developer and he did some tweaks and sent the recovery for the second time. And it worked!