Related
Hello,
I need some help with the transformer firmware upgrade.My tf is rooted,and therefor the update process fails with a orange ! android.I red that an unroot is absolutely nescessary in order to upgrade,but I am looking for a way to do it without refashing and then reinstalling everything.From what I understand both methods listed here: http://is.gd/nGRo5s implie a complete reinstall.
So,any way to get the update without re-installing anything ?
Thanks.
There is a way to flash the update without reinstalling everything, but you need to change your recovery.
A non-stock recovery will let you flash a modified OTA that will let you keep root. Or even better, just flash a rooted stock image.
Great !
Do you have a link to the modified recovery I should use and one to the modified FOTA ?
I assume I would be doing this using the update.zip function of the modded recovery ?
Thanks for the help !
Roach has a modded version of Clockworkmod
http://forum.xda-developers.com/showthread.php?t=1213723
I'm not sure anyone has posted a 8.6.5.13 rom yet.
Edit: the OTA will break root since it will flash a secure boot.img.
---------- Post added at 08:16 PM ---------- Previous post was at 07:59 PM ----------
Actually, if you have the stock recovery, there will be a few extra steps to flash CWM.
You can 1) use nvflash and modify the commands so that it doesn't erase everything or 2) use terminal and flash the recovery through the staging partition.
Then, after you have a working recovery, you can modify the OTA to flash without breaking root or giving you a secure boot.img.
---------- Post added at 08:55 PM ---------- Previous post was at 08:16 PM ----------
I think terminal will be easier since Roach packed up his recovery as a blob. What a guy!
1) download the zip file from Roach's thread
2) unzip it and you'll find a file called recoveryblob- save this to your external SD card
3) use adb or terminal and type
Code:
su
dd if=/Removable/MicroSD/recoveryblob of=/dev/block/mmcblk0p4
reboot
The last piece is zero-pee-four. Be sure to get this right or else you'll be gravely inconvenienced. Your TF will reboot and CWM ala Roach will flash. You'll see a turquoise progress bar and then your TF will reboot.
edit again: daoist posted this already http://forum.xda-developers.com/showthread.php?t=1281161
once you have clockworkmod, go to his thread and flash via clockworkmod.
Happy Flashing!
Well,that's a precise answer ! I'll do the flah soon and will update this thread.Thanks for the help !
Is it possible to take a stock rom and unzip and take the recovery image and just zip it and flash it in TWRP to get stock recovery back?
Look in the development thread, I believe tdunham has a Odin flashable stock recovery. I'm not sure if anyone has made a flashable zip. I think it's possible.
---------- Post added at 06:38 AM ---------- Previous post was at 06:17 AM ----------
I have looked and can't find it. I was wondering why you want it though. Just curious.
metalfan78 said:
Look in the development thread, I believe tdunham has a Odin flashable stock recovery. I'm not sure if anyone has made a flashable zip. I think it's possible.
---------- Post added at 06:38 AM ---------- Previous post was at 06:17 AM ----------
I have looked and can't find it. I was wondering why you want it though. Just curious.
Click to expand...
Click to collapse
Because I have a client that I rooted their phone and they don't want to have customer recovery. They want the phone as stock as possible so this way if they have to take it back to sprint they can just have SuperSU uninstall itself and not worry about Sprint. I'm hoping that I can just zip with the recovery image and just flash it in TWRP.
I'm pretty sure there is a stock recovery img file floating around that you can use an app called flashify to flash it with.
SU4TL-44 Stock Image for XT1254: https://mega.nz/#!v4QWiITb!_0jWWzE4KWCEgT__C36rYe0vaTzGKcEFsZm0vvBtLBg
Flash with TWRP.
This package will flash every image in the SU4TL-44 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, revert to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Thanks to @firstEncounter for letting me incorporate his flashable zip into this package.
Will have to download this later. Looked to go back to stock and wait for mm to come out.
Sent from my XT1254 using Tapatalk
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
No it won't relock boot loader just installed it you will not be rooted and twrp will ask you if you want to root before reboot if you click no and want to at a later point just go back into boot loader by doing vol down power combo from power off and select open boot loader and when you click to reboot it will ask you again if you want to root then you can just slide to install
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
Correct
Can I install viper and su along with this?
MazinDLX said:
Can I install viper and su along with this?
Click to expand...
Click to collapse
Sure. Just flash the rom first and the mods second.
TheSt33v said:
Sure. Just flash the rom first and the mods second.
Click to expand...
Click to collapse
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
MazinDLX said:
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
Click to expand...
Click to collapse
I've never tried to install an image via ADB before. Did you mount the image elsewhere and extract the system folder, and then ADB-pushed that? If not, your bootloop is probably because there's just a big, unextracted system.img on your system partition, and not the actual files within it. Why not just flash it with TWRP? When I tested it, I flashed it via TWRP and it worked.
If you really don't want to flash it via TWRP for some reason, you can extract the system.img from the zip and flash it using fastboot (fastboot flash system system.img).
EDIT: Oh wait, I think I understand now. You just used ADB to put the zip on your phone, and then you installed it with TWRP. Got it. Well my next question is why use ADB at all? Why not just plug in your phone while it's booted into TWRP and use the native MTP to transfer files?
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
This package only flashes /system. CM flashes its own boot.img, which is why this isn't working for you. I'll try to find some time tonight to add in the other images in the stock firmware to this package. Sorry about that.
firstEncounter said:
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
Click to expand...
Click to collapse
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
TheSt33v said:
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
Click to expand...
Click to collapse
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
firstEncounter said:
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
Click to expand...
Click to collapse
I'm not entirely sure how to write a script to flash those in TWRP. For boot and system, it's easy because the devices that they are flashed to match the names used by fastboot. Bootloader and radio seem to be a little different though. When I list the contents of /dev/block/bootdevice/by-name, there is no "motoboot" or "radio," which is what fastboot uses when you flash these. I do see "aboot" and "modem," and I'm pretty sure those are the targets I'm looking for, but I don't want to go flashing things unless I'm 100% sure. Since there's not a huge demand for figuring that out, and boot + system is all people will need in 99% of cases, I'll leave them out. Thanks though!
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
MazinDLX said:
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
Click to expand...
Click to collapse
No, but I appreciate the thought. Donate to this guy instead. He does way more than me and also needs it way more than me: http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
TheSt33v said:
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
Click to expand...
Click to collapse
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
bigv5150 said:
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
Click to expand...
Click to collapse
Awesome! That's why we do this
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Stefan-Duisburg said:
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Click to expand...
Click to collapse
you can flash from sd card
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
tolgazorba said:
you can flash from sd card
Click to expand...
Click to collapse
You can find the same software number at the top of the device or the numbered software in the android file host ziand folder
Hello @tolgazorba.
Thank you for your answer. Right now I'm heading to work, but I will try your Advise this evening. Fortunately i downloaded a ruu zip matching with my firmware (2.55.bla bla) and matching with my cid as well. I will report if everything worked, or, hopefully not, not.
Thanks again
Stefan
hello
no problem I would like to explain in detail but my english is very bad
Hi there. That advice was great, everything works now fine again. I guess I let my hands off rooting for now, at least there's an official LOS for this device lol
Thanks again
En joy
You're welcome
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Merhaba
are you serious
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
lulonen said:
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Click to expand...
Click to collapse
because I need help with something
---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------
my problem is that i can't assign custom rom to your device why do you think
I thinked that's because of slots
Hi
buddy what exactly is the problem
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
lulonen said:
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
Click to expand...
Click to collapse
Maybe just flash actual firmware.zip with sdcard as i have done? With that you are back on full stock and you can root again etc...
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
hi
lulonen said:
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
Click to expand...
Click to collapse
You are a very old user, I think you know how to do it
Hi
full rom viper twrp with temporary rom flash without wipe i not temporary to permanent summer device
can't boot TWRP and dont have stock rom without wipe.
Don't you know why I can't boot temporary TWRP? download mode always stuck at booting
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
isn't full wipe?
don't remember but EU version (043). I am on LeeDrOiD U12 V1.3
re-install the same rum without deleting or update it with adb sideload
tolgazorba said:
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
Click to expand...
Click to collapse
If I only had a backup different to TWRP.... ;-(
Does anyone happen to have the stock ColorOS recovery.img for this device?
Thanks!
Jaernyx said:
Does anyone happen to have the stock ColorOS recovery.img for this device?
Thanks!
Click to expand...
Click to collapse
I've been looking for it also. I couldn't find it in the ozip OTA files.
I have the Chinese variant and want to test the Chinese TWRP, but need the stock recovery just in case...
it's all inside the file system.new.dat.br I'm also trying with the global version
Kratong said:
it's all inside the file system.new.dat.br I'm also trying with the global version
Click to expand...
Click to collapse
I extracted that file. There are a lot of folders. Not sure where to look. Any idea?
with which program? I can't do it I need a fastboot rom
I'll take a look in the system file as well when I get off work.
Smart of you to back your stuff up before diving in. I was trying to see if I could create a rom for my device but I believe I borked my partitions up.
The twrp from wzsx150 in the other thread doesn't boot on my device so I'm hoping the stock recovery image will get me on the right path. I was able to make a bootable twrp but the system partition doesn't mount correctly so I can't flash with it.
I'm pretty new to this stuff but learning more every time I work on it, haha. Should have taken correct precautions though.
Jaernyx said:
I'll take a look in the system file as well when I get off work.
Smart of you to back your stuff up before diving in. I was trying to see if I could create a rom for my device but I believe I borked my partitions up.
The twrp from wzsx150 in the other thread doesn't boot on my device so I'm hoping the stock recovery image will get me on the right path. I was able to make a bootable twrp but the system partition doesn't mount correctly so I can't flash with it.
I'm pretty new to this stuff but learning more every time I work on it, haha. Should have taken correct precautions though.
Click to expand...
Click to collapse
I can't fastboot boot that recovery either and I have the Chinese variant.
Did you do the disable verity etc before trying to boot until your TWRP? Or it could be encryption that's preventing you from viewing the system partition? Might need to format data?
None of these things I'm willing to try without a backup stock recovery though
anandlal said:
I can't fastboot boot that recovery either and I have the Chinese variant.
Did you do the disable verity etc before trying to boot until your TWRP? Or it could be encryption that's preventing you from viewing the system partition? Might need to format data?
None of these things I'm willing to try without a backup stock recovery though
Click to expand...
Click to collapse
I poked around all the dat.br files in the OTA update except the numbered version files and wasn't able to find any recovery.
Unfortunately, I've already fully wiped and it still wont' mount. It kind of seems like my system partition got completely nuked, although tbh I'm not entirely sure how I did that
That being said, I tried directly mounting /system, but I get the error that a block device is required. I checked the fstab files on what I have available and it seems to point to a file that isn't on my device. RIP, haha.
I'll continue to see what I can figure out though. Happy to know it doesn't boot for you actually, as I thought it not booting was due to me gunking up something. Oh yeah, I have a Chinese variant too.
Jaernyx said:
I poked around all the dat.br files in the OTA update except the numbered version files and wasn't able to find any recovery.
Unfortunately, I've already fully wiped and it still wont' mount. It kind of seems like my system partition got completely nuked, although tbh I'm not entirely sure how I did that
That being said, I tried directly mounting /system, but I get the error that a block device is required. I checked the fstab files on what I have available and it seems to point to a file that isn't on my device. RIP, haha.
I'll continue to see what I can figure out though. Happy to know it doesn't boot for you actually, as I thought it not booting was due to me gunking up something. Oh yeah, I have a Chinese variant too.
Click to expand...
Click to collapse
Damn... That's insane! So I guess you have to wait for the stock recovery to be available before you can go back to the stock rom.
What I do like about the stock recovery is that your have the option to go online and install the stock rom.
Kratong said:
with which program? I can't do it I need a fastboot rom
Click to expand...
Click to collapse
Convert system.dat.br to system.dat (brotli)
Convert system.dat to RAW system.img (sdat2img)
Extract system.img (imgextractor)
I installed the twrp chinese version on the global version now i am rom china I wanted to go back but I can't go back to global
Kratong said:
I installed the twrp chinese version on the global version now i am rom china I wanted to go back but I can't go back to global
Click to expand...
Click to collapse
You were actually able to install the CN ROM in the Global variant?!
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Kratong said:
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Click to expand...
Click to collapse
What was the steps you took to go from EU to CN?
I was actually considering going from CN to EU but thought I'd was not possible due to the different partition sizes for system etc..
I can't convert system.img to raw system.img for flash with fastboot can someone post it already converted? for rmx2076.thanks
Kratong said:
I can't convert system.img to raw system.img for flash with fastboot can someone post it already converted? for rmx2076.thanks
Click to expand...
Click to collapse
this link system.img for rmx2076
https://bit.ly/2Yse5ue
i flashed system.img with fastboot reports this error invalid sparse file at header magi. what should i do?
Kratong said:
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Click to expand...
Click to collapse
They just released a flash tool. Let me know if this works for you.
https://www.realmebbs.com/post-deta...subForumId=1156882636577189888&language=zh-CN
thanks later I look at it but is it ok for the global version too? my situation is now this I managed to install the Chinese rom on rmx 2076 involuntarily but the modem part doesn't work everything else works
Kratong said:
thanks later I look at it but is it ok for the global version too? my situation is now this I managed to install the Chinese rom on rmx 2076 involuntarily but the modem part doesn't work everything else works
Click to expand...
Click to collapse
From the looks of it. You just need to have your phone in fastboot mode and select the file you want to flash. So you can try selecting the Global ozip and see if that would bring you back to stock.