Related
Is it possible for anyone to create/point me to a downloadable stock ROM? I mean literally STOCK, as in, nothing changed. I think that might be the only way for me to get back to being able to receive OTA updates without fastbooting (which I have tried to no avail).
Thanks!
there you go http://forum.xda-developers.com/showthread.php?t=1416058
Yeah, see...fastboot doesn't work for me - already tried it a bunch of times. For some odd reason. I mean, does someone have a stock ROOTED ROM I could flash. As in, something with all apps preserved as if the device were not rooted. That way, I can take the OTA update (and break root, but at this point I just don't want to be trapped in OS 2.3.5 forever). Thanks (again)!
Are you able to access stock recovery?
Yes, I am. Will that help?
on my maxx, having the same issue as you, i factory restored, i guess that might have replaced/fix any corrupt files and i was able to fastboot. Unfortunately, i speak from personal experience and not knowledge of the operating system. good luck.
I did a factory data reset and it did not fix the problem, sadly. Looks like I'm in a hole with no ladder out lol. I can always hope that a stock rooted ROM is available so I can use my recently-recovered root to flash and then take the OTA over that, if possible.
http://www.droidrzr.com/index.php/topic/457-rom-totally-stock-rooted-748/page__pid__14816#entry14816
Link is dead; they're looking to fix it though I think. Thanks though! I'll give it a shot.
If you can take the update, this http://forum.xda-developers.com/showthread.php?t=1492708 can root the new 2.3.6
Doomlords method still can unroot if need be.
Sent from my DROID RAZR using xda premium
Thanks! I'll keep it in mind. Right now I'm looking for a way to be able to get the update though
Yeah I'm in the same boat. Need this link to work!!! Can someone please post another working link?
http://forum.eternityproject.eu/mot...f7/official-motorola-razr-roms-thread-t4.html
I hope this helps
I think we just need a stock ROM, not the OTA. We can't flash the OTA (even an older one) like a ROM, right?
Atlas.rouge said:
I think we just need a stock ROM, not the OTA. We can't flash the OTA (even an older one) like a ROM, right?
Click to expand...
Click to collapse
That is the stock rom. The second post includes 2 stock versions and 2 OTA. Just download the stock Rom. Atleast i think thats a flashable ROM
Theres this also
http://forum.xda-developers.com/showthread.php?t=1362956
Is the only option to flash these via adb and rsd lite?
Question: (rather than creating new thread)
what's the different between ROM and Fastboot files? Examples?
Coz i downloaded Brazil.en fastboot, use RSD Lite, and flashed my GSM Rogers RAZR. works great.
But i also have SafeStrap installed, and I can make backup (and restore) from it. Are those ROMs? Or just backup files?
I thought people flash their phones using mod ROMs using CWM/Safestrap too?
I know OTA is over-the-air, but u can also download and manually install "OTA" updates? so... are they OTA ROM then?
or just OTA "files". like backup files CWM made?
thx for explanations
MBL85 said:
Is the only option to flash these via adb and rsd lite?
Click to expand...
Click to collapse
That was the way I did it, Ive read about a few others like;
motofail
DroidRAZRUtility1.4LITE
vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
But flashing with RSDlite was how I did it and it worked fine, just wish I had the original ROM with all the bloatware just in case....
Yeah, see for some reason fastboot doesn't like me, which is why I'm trying to get ahold of a complete stock ROM lol. I know that fastboot *works* all the time, but rather than go through the hassle I was just hoping someone had a spare total stock ROM floating around haha
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
upndwn4par said:
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
Click to expand...
Click to collapse
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
I just sold mine but will look in PC history. My matrix was stock 4.5.145 and I rooted it. I remember failing a few methods till I found one that worked. If I figure out what I did I will post it for you. If not fruitcake is best way
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
upndwn4par said:
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
Understood, thanks for the explanation.
UnlockRoot couldnt gain root access
I will attempt your suggestions Thanks very much for the guidance, its invaluable
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
KetoSoi said:
Unless some one figures out what motorola/att did with 145 to completely screw root ...
Click to expand...
Click to collapse
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
upndwn4par said:
Let me know how things go with the above before you even consider this.
Click to expand...
Click to collapse
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
ravilov said:
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
Click to expand...
Click to collapse
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
KetoSoi said:
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
Click to expand...
Click to collapse
Wow, that's just bizarre. Not sure what to think here.
I meant something like
Code:
moto-fastboot erase preinstall
KetoSoi said:
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
Click to expand...
Click to collapse
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
upndwn4par said:
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
Click to expand...
Click to collapse
Very odd some cannot root. I was on permalocked bootloader and still rooted after soak
Its sad, because the 145 update seemed like it made the phone a little snappier, and the screen was a pinch smoother.
What do you guys think about applying the CWM Zip for update 4.5.145 in my situation? Would that be safer?
Uh oh.... you guys ran away! LOL
I was able to flash the 145 update via CWM from NYG-SBXLII's handy zip file
No real problems, 145 running fine WITH root intact. Awesome
Had to blow away the recovery-from-boot.p file afterwards, and re-flash CWM Recovery, but it was all good.
Updated SU and bin's, good to go.
affiatic said:
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
Click to expand...
Click to collapse
This worked for me too with 4.5.145, followed it exactly and had no problems. Thanks!
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
How did you unlock the bootloader for firmware 4.5.145? I've been looking everywhere on how to do it safely!
upndwn4par said:
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
hello, ive been using 4.5.145 and was unable to root it, the problem with mine is that when I try to use the preinstall method it chokes when i type the "cp /preinstall/su /system/bin/... there was a message cp write error: no space left on device.. I have tried everything (almost) to root it but was unlucky.. then i saw this thread http://forum.xda-developers.com/showthread.php?t=2153422 ... i wanna try your suggestion but cant find the zip file in suggestion 1 and the 141 fruitcake you made on suggestion 2 and cant find file on option 3.. please do help me.. I have unlocked bootloader and have rom racers cwm.. thank you and more power..
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
The problem with flashing oem firmware
medwatt said:
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
Click to expand...
Click to collapse
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
mtyler7807 said:
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
Click to expand...
Click to collapse
When you say "update", do you mean clearing the OS and installing a new one from scratch ? Does that mean after the update all the consumer cellular additions will go away and there will be no trace of it ?
If updating seems difficult now for the consumer cellular versions, what will we do when they release Lollipop ?
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Assuming they release the CC version of lollipop, will there be any problem if some of the system files have been changed? For example, I've deleted some system apps that I never use and changed the boot- and flash-screen files. Will the update fail because of that ? I'm asking this because I saw a video made by one of the forum members here when he was trying to install the v148 update. He had to uninstall everything and return the system to default before updating. If that is so, then I guess no Lollipop crying::crying for me !!
Given that Lollipop is still some months away and the lack of any meaningful activity on the HAM2, why don't we prepare our HAM2 for who-knows-what. I'd like to get a grip on a my phone now instead of getting swamped by error messages when Lollipop gets released or we get custom firmware.
There's this thread [http://forum.xda-developers.com/showthread.php?t=2315547] which explains how to extract the individual image files from the huawei update app.
Do you have the CC version of HAM2 ? If so, will you be trying to flash the image files because extracting the image files seem straight-forward ? I'm actually a bit nervous doing it myself because I've always flashed my other devices when it has been confirmed to work. What I'm wary of is I'm not sure that the device software in the v148 update app is 100% compatible with the CC variant that I own ! How can one be sure of that ?
I've downloaded v148 update file and extracted the files you mentioned. Instead of taking screenshots of the contents of the image files, I've recorded a small video. I can see the boot.img and system.img but no recovery.img. There are also other files. Take a look at the video. The question now is what to do with these files and more importantly what are my chances of unbricking the phone if it bricks !!
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you seen the video I uploaded ? Is it the "full download"? Can I flash it ? Will the phone brick ?
I read your posts on the subject. But it seems you have changed some system apps and the camera is not working as it should. I have already downloaded the 148 file and extracted the system.img and boot.img files. Can I flash these or do I have to use the files you uploaded on google drive ?
The question is why didn't you use the v148 stock ? I already have the v148 stock. Will it brick my phone if I flash the image files ? If not, why did you have to add extra files there such that the camera is 8MP instead of 13MP. Also, why is the hotspot always enabled ? Is that the case with people with the original stock ?
Man, I'm still waiting for your reply !
medwatt said:
Man, I'm still waiting for your reply !
Click to expand...
Click to collapse
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
290 said:
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
Click to expand...
Click to collapse
"For whatever reason mtyler7807 is trying to reinvent the wheel", Ha Ha. I spent about 2 weeks working on this phone when I first got it. With this phone it has more partitions than what is included in the backup with TWRP. TWRP is made for backup and restoring the files that get changed, the other partitions don't change. So when I first started experimenting with this phone I got a full 148 backup with no data and installed it. I had problems, the custom.bin points to a different cust/us/ folder (because it is for a different carrier) , I had to rename that folder and found I have no more 4glte only H/H+, So I had to get the original cust folder from the guy and copy it to the phone. Still and only H/H+. It was okay for then because I testing. Next Viewed my system specs and saw that pretty much half half phone was 148 and the other half was 132.
I have Redone my complete back since I posted the last one with google camera with 13mp support( rather have border transparency). I made a post asking people summit backups. You have to do a little research, did my research and got help from the forum guys. If you want 148 on your CC version you will have to extract the update and fastboot img files (ex.fastboot flash system system.img). The name of the file is the partition name.
From my understanding twrp does a nand backup. Which is more like an image of nand. So restoring an image from a stock phone would also give you the stock partition table no?
It has been a while since ive played with android on such a low level. When it came time to update my HP Touchpad to JB i had to manually create the partition table manually to make it fit. Eventually a script was created that automatically made the changes to the file system. Perhaps a solution along those lines could be useful in getting the stuck firmware on the CC phones? The file system would only need to be created on initial flash to the stock firmware.
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
medwatt said:
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
Click to expand...
Click to collapse
Here is what k2thejx5 said after flashing a backup from a stock phone.
k2thejx5 said:
What's weird is when I flashed the stock file and tried to upgrade, it wouldn't work. The kernels were different so I had to go back to stock consumer rom. Also, while using the rom you posted.. I lost my toggles and had to use a different app. What also was very weird, after flashing back to the stock consumer rom, I had tethering! Don't get it lol.
Click to expand...
Click to collapse
-Do what I did makes your phone a complete oem, All that is need to be done is to flash a splash screen.
-How would I know if updates will work since 148 is the latest version for oem, can't test that tell lollipop.
-I'm not pushing anyone to install my image, I got about 30 pm's to post my recovery to enable hotspot and to get those toggles backup at the top. Alot of people messed up and lost them flashing that original twrp recovery under developer. Alot of others wanted the hotspot without the head ache of going through the research.
And for the people with problems with there phone that want 148 and updates with no problems, You should have brought a OEM and stayed away from sears or target or took it back to the store if you were not ready to take on the challenge of fabbing up your phone. Or just deal with the factory image and hope for lollipop.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
Me and k2thejx5 was trying to fix the problem with the twrp recovery originally posted on this site. That one is not mine. Read the post. That firmware took our toogles away. You have to read this forum a little more.
Ok man, thanks for the reply. Two last question:
-For as long as you've been using your phone with your image files, have you been noticing problems like "unexpected crashes", trying to launch something and its unresponsive lie APN
-Is this the latest file you recommend : [https://drive.google.com/file/d/0BwnSk8BOQp3wV0JMWnJGc3RBTzQ/view]
Thanks.
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
mtyler7807 said:
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
Click to expand...
Click to collapse
All right then. Upload it when you're ready !
Hello everyone!
I've been very happy with my rooted M9 for the last few months but now a system update message on my screen and I'm trying to figure out what to do about. I seem to recall when I rooted my phone that there could be complications if I install a system update on a rooted phone (like making a Nandroid Backup) but I'm finding scarce information on the topic. Does anyone here have some advice about this?
Rom...
http://forum.xda-developers.com/showthread.php?t=3083799
Firmware...
http://forum.xda-developers.com/showthread.php?t=3073355
Follow the second link above.
You will need to restore the factory system.img using TWRP (exFAT or NTFS for external USB as file is > 4GB).
This puts the modified system (root) back to stock so the update will run successfully.
Flash the original recovery for you system version too.
Then you can accept the OTA and then root the phone again.
Thanks for the responses! I'm still uncertain about a few things so tell me if I have this right.
First I need to restore the factory image. Is that a guy named OJM is talking about on this thread? (http://forum.xda-developers.com/sprint-one-m9/general/rooting-guide-t3073004)
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
Click to expand...
Click to collapse
In that case, what is a system.emmc.win?
Then I flash the original recovery...what are you refering to when you say "original recovery"?
After that my phone should be locked again and I can go to that second link, download the latest firmware and flash it. And then I can unlock and root my phone again.
Edit: So it looks like someone has made a guide on how to get the OTA updates (if you use the right words in your search). It looks no one done anything with it since May so maybe it still works? http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Sim-X said:
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Click to expand...
Click to collapse
That was what I ended up doing. Had few bumps on the way but I managed to get everything working. Thanks for the help everyone!
RUU
Sim-X said:
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Click to expand...
Click to collapse
hi sim I have a question the only thing I got to make sure is that the phone is S-OFF and nothing will happen because I read that also the bootlooder had to be lock again so I'm not sure
Hey guys! Unfortunately I bricked my new HTC Desire 626s while fiddling around with xposed for lollipop after successfully rooting the phone and installing cyanogen recovery. I think if I flash the stock rom on the phone through either adb or cyanogen recovery I can unbrick it, but I have been unsuccessful in finding this file on the internet. Would anyone care to give me a link or upload the stock firmware/rom of this phone? It would really help me out, thank you!
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
es0tericcha0s said:
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
Click to expand...
Click to collapse
Umm.. Okay so I guess I'll give you my phone's info? WAIT DOES THIS MEAN YOU CAN PROVIDE A DOWNLOAD!? IM SO EXCITED, UH OK HERE
- HTC Desire 626s
- Metro PCS USA
- Current firmware version : 1.06.1550.7
ANYTHING ELSE?? IF YOU CAN GIVE ME THAT DOWNLOAD LINK, MY MOM WONT KILL ME:crying::crying::crying: (she's really pissed :laugh Thank you btw!
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
es0tericcha0s said:
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
Click to expand...
Click to collapse
I tried this before my phone got ****ed and it worked:good:! If you can help me dude that'd be great. After uninstalling or changing some stuff in priv-app on my HTC Desire 626s, when I rebooted, it would just stay in a boot loop with the optimizing app message. Any ideas?
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
es0tericcha0s said:
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
Click to expand...
Click to collapse
I believe I uninstalled the dialer and its service in an attempt to replace them with the stock lollipop ones. How do you install TWRP on this phone? My mom has the same phone and its also rooted but hers actually works so I was thinking since TWRP has a nandroid backup setting, I could simply do a nandroid backup on hers and flash it on to mine to see if it will boot up. What do you think? And for the optimizing apps thing, it would finish optimizing, say starting apps, reboot and then optimize again and repeat. Thanks for the help btw, I really hope we can fix this.
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
es0tericcha0s said:
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
Click to expand...
Click to collapse
Do you have the TWRP recovery file for me to download?
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
es0tericcha0s said:
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
Click to expand...
Click to collapse
I installed Cyanogen recovery before flashing Xposed and the uninstaller. I thought you had the TWRP recovery img for my phone which is why I asked. I believe some developers are working on a Clockworkmod recovery for this phone which is basically the same thing as TWRP recovery, right? Anyways I guess I just have to wait until that comes out, but I was wondering if anyone who somehow got a hold of the stock rom could upload it for us to use. It would be really helpful
ClockWorkMod is the recovery that Cyanogen uses. That is able to perform nandroid backups as well.
You have to unlock the bootloader, then if you messed up your stock rom and you've updated it to something newer than what Samsung gives for a stock recoverable rom, you must first use the tmobile vers, let it fail, and then use metropcs vers.
If you messed up recovery or anything it will all go back to stock after flash.
Next just copy superuser zip file to phone, go to download mode and adb flash cyanogen recovery img. Then reboot to recovery, choose to flash update, and find the superuser. zip and flash it, voila.
https://www.mediafire.com/?8o6qtn7hlsec0zj,yqbbzb7divlcvvc
Kitkat, anyone?
Does anybody have a stock KitKat ROM for this device? I'd like to try to bypass the FRP, but am stuck on what must be either a marshmallow or lollipop ROM.
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Issue is fixed
BigCountry907 said:
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Click to expand...
Click to collapse
I ended up fixing it using some ADB commands as noted in the "Well, I may have found..." thread. It'll be nice to have this phone out of my life. The day I had to spend with it was two days too many.