Related
Ok, so after the announcement of the 3.1 update at IO yesterday, were all eagle awaiting the 3.1 update.
For those of us in europe, with 3G xooms we need a different update so don't try flash anything that is currently available.
Second and most important. There are NO Stock boot images for 3G europe, we need someone who has stock recovery to dump it and get in touch with me. WE CANNOT UPDATE IF WE INSTALLED CLOCKWORK MOD.
Once we have a stock recovery image I can post all the stock images for us to flash back to stock for the update.
Use these commands to dump the recovery image (you need to be rooted and/or have a custom kernel like Tiamat (or the one in my thread) installed so you can remount, you may also need to install busybox (use Busybo installer by Stericson from the Android Market, don't forget to open and run it after you install it):
Code:
adb remount
adb shell dd if="/dev/block/platform/sdhci-tegra.3/by-name/recovery" of="/sdcard/recovery.img"
adb pull /sdcard/recovery.img
That's it, the image will be on your sdcard and copied to your computer, please upload or PM me a link.
Thanks
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
I had to add "platform" to the path:
adb shell dd if="/dev/block/platform/sdhci-tegra.3/by-name/recovery" of="/sdcard/recovery.img"
Click to expand...
Click to collapse
Hope I did it all right after rooting the device (by your manual - thanks in advance for this!).
Riffer said:
I had to add "platform" to the path:
Click to expand...
Click to collapse
You're right, sorry I typed it from memory, will update it now!
That's... odd...
The kernels from the boot image that you circulated a while back, plus the kernel from this recovery image, are different.
They should be the same.
(The recovery ramdisk ro.build.version.release says 3.0.1, maybe the boot image is from 3.0? Has the MZ601 got 3.0.1 yet?)
ydaraishy said:
That's... odd...
The kernels from the boot image that you circulated a while back, plus the kernel from this recovery image, are different.
They should be the same.
Click to expand...
Click to collapse
That's normal ... a recovery image would probably have a light weight stripped down kernel, since it doesn't need to boot and run the full OS, just hte recovery OS.
It's also possible that the recovery might be the same as the US one, and the US one runs a differnet kernel to the euro one, so it's not necessarily a problem that it's different.
Oh, and any chance of a link to the recovery image you've dumped? Please.
alias_neo said:
That's normal ... a recovery image would probably have a light weight stripped down kernel, since it doesn't need to boot and run the full OS, just hte recovery OS.
Oh, and any chance of a link to the recovery image you've dumped? Please.
Click to expand...
Click to collapse
No, they should have the same kernel. It's designed that way. (Remember, when you get an OTA, you get a recovery-from-boot.p patch that runs on startup to repatch your recovery image back to stock -- it's deliberately based on the boot image, so the patch is as small as possible)
I didn't dump the recovery image -- look a few posts up (I _still_ don't have a device yet )
ed. And I don't think a US MZ601 is out yet...The above dump looks like it's from a German Xoom, based on ro.product.locale.region.
ydaraishy said:
Has the MZ601 got 3.0.1 yet?)
Click to expand...
Click to collapse
Yes. Mine does have it. Got it without any branding from www.sparhandy.de yesterday.
Should I mention I am german?
alias_neo said:
Oh, and any chance of a link to the recovery image you've dumped? Please.
Click to expand...
Click to collapse
Mine is attached above? Or do you say that to ydaraishy?
Riffer said:
Mine is attached above? Or do you say that to ydaraishy?
Click to expand...
Click to collapse
Sorry, didn't see your edit.
EDIT: @ydaraishy: Interesting, I wasn't aware of this as I have never ran an OTA before in my life, and my XOOM was at 3.0.1 when it was released.
So, I wonder what the deal is here, will the euro OTA come with a full kernel? Maybe the method I used to split the kernel and ramdisk I posted (in order to root it) caused some change? How are you comparing them?
alias_neo said:
Sorry, didn't see your edit.
EDIT: @ydaraishy: Interesting, I wasn't aware of this as I have never ran an OTA before in my life, and my XOOM was at 3.0.1 when it was released.
So, I wonder what the deal is here, will the euro OTA come with a full kernel? Maybe the method I used to split the kernel and ramdisk I posted (in order to root it) caused some change? How are you comparing them?
Click to expand...
Click to collapse
No, they'll binary patch it like usual.
I split the kernel and ramdisk of the recovery image, then the boot image that you had posted a while back for root, then md5'd both kernel images.
Got my T-Mobile Xoom 3G (3.0.1; MZ601; H.6.1-38-5) today and dumped the recovery.img just after flashing rooted boot.img.
Hope this helps.
Thanks guys, hopefully i can use these to sort something out for us when we get 3.1 update finally.
I also have a T-Mobile Xoom and I've used Clockworkmod Recovery to make a dump via dd of system and boot.
All togheter we should now have a complete set of the MZ601 H.6.1-38-5 Firmware.
I put it togheter into one rar-file and uploaded it. But I am not allowed to post links here because of not enough posts.
I will send it to you via PM, hopefully someone of you can post it.
Hope this helps.
MediumO said:
I also have a T-Mobile Xoom and I've used Clockworkmod Recovery to make a dump via dd of system and boot.
All togheter we should now have a complete set of the MZ601 H.6.1-38-5 Firmware.
I put it togheter into one rar-file and uploaded it. But I am not allowed to post links here because of not enough posts.
I will send it to you via PM, hopefully someone of you can post it.
Hope this helps.
Click to expand...
Click to collapse
Your zip you PMd me says boot, recovery and system, surely all 3 can't be stock if you installed clockwork mod to dump it, so which two are stock?
Ok, this one is exactly identical to mine - says Winmerge.
Riffer said:
Ok, this one is exactly identical to mine - says Winmerge.
Click to expand...
Click to collapse
Which one?
I used the recovery of Riffer. System and boot are stock from my device.
I just put them togheter in one archive to get a full set.
MediumO said:
I used the recovery of Riffer. System and boot are stock from my device.
I just put them togheter in one archive to get a full set.
Click to expand...
Click to collapse
That's great. Now we just gotta wait for 3.1 in Europe!
I have been fallowing this forum for a long time and also I got my Xoom from CPW couple of weeks ago and I have to say that I'm really waiting for this update so bad, just because many people has been reviewing it and they say is really a change in performance, sometimes I find that my Xoom is quite heavy, more when I'm trying to surf the web, and sometimes when I come to the forum from it, and I will like to be an active member of this forum as well, I will try to help with anything I can and I just rooted my Xoom with neo guide.
sorry if my english is not so good.
I'm in London at the moment
and Galaxy SII owner as well
Hopefully 3.1 will show up in Europe soon. I read somewhere that T-Mobile Germany had also planned to release the update on 5/11. But no evidence for that until now.
Otherwise we have to port the CDMA Rom ;-)
MediumO said:
Hopefully 3.1 will show up in Europe soon. I read somewhere that T-Mobile Germany had also planned to release the update on 5/11. But no evidence for that until now.
Otherwise we have to port the CDMA Rom ;-)
Click to expand...
Click to collapse
There will be non of that frankenfrak here sonny. We get our own 3.1 or we all go down swinging. :-D
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
Hey Guys this ONE CLICK TOOL is base on KennethPenn one click tool (Thank to him)and i updated the script to fastboot.exe flash recovery openrecovery v2.6.0.0 Evita.img I'm not responsible if anything happen to your phone.I believed U should know what u doing to install recovery but if don't...here's the original TWRP recovery thread (thanks to eyeballer) and check TWRP website http://www.teamw.in/project/twrp2/99 for installation instruction.If does work u know what to do with that thanks button....:good::highfive::good:
INSTALLATION is very easy that's why it called ONE CLICK TOOL ....Connect device to PC.....extract the zip file.....open folder where u extracted the files ....double click on install.bat (WINDOW ONLY)
UNLOCK BOOTLOADER>INSTALL RECOVERY>ROOT>INSTALL CUSTOM ROM> HIT THANKS BUTTON......ENJOY
Also using goomanager from the Play Store is pretty easy to use.
Sent from my HTC One X
howsleyd said:
Also using goomanager from the Play Store is pretty easy to use.
Sent from my HTC One X
Click to expand...
Click to collapse
I did three time earlier today all i got is error....maybe Goomanager is down or something....and read on last couple page from recovery thread couple people can't install script also ..... so thats y this idea came up and asked Kpenn if that even possible.
Is the bolded, multicolored, and strangely sized text really necessary?
bobtentpeg said:
Is the bolded, multicolored, and strangely sized text really necessary?
Click to expand...
Click to collapse
Coz alot of people didn't read small text and keep asking the same and unnecessary question .....
Dear ted77usa (OP),
what is the difference between your release and the one posted here posted 5 days ago?
[RECOVERY][ONE-X/EVITA]TWRP 2.2.0 with on-screen keyboard! [2012-07-12]
Please advise.
Thanks!
howsleyd said:
Also using goomanager from the Play Store is pretty easy to use.
Sent from my HTC One X
Click to expand...
Click to collapse
yup! it's easy as pie
BIGMOH said:
what is the difference between your release and the one posted here posted 5 days ago?
[RECOVERY][ONE-X/EVITA]TWRP 2.2.0 with on-screen keyboard! [2012-07-12]
Click to expand...
Click to collapse
You should notice the thread you posted only contains a link to download the recovery, or says to use goomanager.... The OP did not just repost the recovery, he posted a one-click script to install the recovery for you, instead of using ADB or goomanager.
Yeah yeah, before anyone ELSE has to say it, we all know there are a few easy ways to install a recovery, and now there is one more. If this thread doesn't concern you then ignore it and move along!
bobtentpeg said:
Is the bolded, multicolored, and strangely sized text really necessary?
Click to expand...
Click to collapse
It makes you cooler on teh intarw3bz...ssssh!
freshleysnipes said:
You should notice the thread you posted only contains a link to download the recovery, or says to use goomanager.... The OP did not just repost the recovery, he posted a one-click script to install the recovery for you, instead of using ADB or goomanager.
Yeah yeah, before anyone ELSE has to say it, we all know there are a few easy ways to install a recovery, and now there is one more. If this thread doesn't concern you then ignore it and move along!
Click to expand...
Click to collapse
I also posted a flashable zip in the Official thread if anyone is interested.
BIGMOH said:
Dear ted77usa (OP),
what is the difference between your release and the one posted here posted 5 days ago?
[RECOVERY][ONE-X/EVITA]TWRP 2.2.0 with on-screen keyboard! [2012-07-12]
Please advise.
Thanks!
yup! it's easy as pie
Click to expand...
Click to collapse
Different people have their own preference how to install.....some using adb&fastboot....some use flashable zip that posted couple days ago...some use Goo manager(doesn't work for me always got an error..see third post for screenshot).The one that u refer 5 days ago is original thread from eyeballer using adb & fastboot manually check the website link for more detail ...basically it's all the same it just different way how to install it...and it might not work for everybody....thats y came alot of different way how to install it....that's all and i hope that's clear all the confusion.
Swyped from T3DRO1CS OneXBlueICESense
Thanks! It worked out great AFTER I modified the install.bat file and changed the 7th line to "fastboot.exe flash openrecovery-twrp-2.2.0-evita.img"
Updated OP and install.bat script line 7th to fastboot.exe flash recovery openrecovery-twrp-2.2.0-evita.img
Swyped from T3DRO1CS OneXBlueICESense
I was getting an error "unable to determine img" or something like that and after some research it says it was because the fastboot script was missing "recovery" so I modified it to:
fastboot.exe flash recovery openrecovery-twrp-2.2.0-evita.img
and it worked after that.
Thanks this save me to root the new 2.20.202.7 ATT OTA
Noob question and I apologize but..
Does the phone need to be off or can you install the one click with the phone on?
I noticed on v 2.2.0 the option to wipe battery stats was removed. I got in the habit of letting my battery die, wiping battery stats then fully charging then wiping again every time I flashed a new rom on my atrix to ensure I was getting accurate battery readings. Was this necessary?
Edit: Did a quick Google search..Apparently a Google engineer said it does not improve battery life. I never expected it to, I just thought I would see more accurate battery readings.
May get a one x tomorrow. Question. Can I use this tool to flash twrp and then just install a rooted rom from twrp. My concern is buying a phone with the OTA 2.20 UPDATE and not being able root. Cuz I forsure am not buying phone I can't install a debloated rom on buy so long as I can get a custom recovery image I should be fine.
Sent from my Skyrocket running AOKP 4.1.1 Jelly Beeeaannsss
MrMiami81 said:
Does the phone need to be off or can you install the one click with the phone on?
Click to expand...
Click to collapse
Yes u can.....
filthyfnj24 said:
I noticed on v 2.2.0 the option to wipe battery stats was removed. I got in the habit of letting my battery die, wiping battery stats then fully charging then wiping again every time I flashed a new rom on my atrix to ensure I was getting accurate battery readings. Was this necessary?
Edit: Did a quick Google search..Apparently a Google engineer said it does not improve battery life. I never expected it to, I just thought I would see more accurate battery readings.
Click to expand...
Click to collapse
I Got Used To That Option As well.....but U should check on Official Twrp Site Or Thread they The One made the recovery...maybe on their next Update they would add it that option....
Pixelcreativ said:
May get a one x tomorrow. Question. Can I use this tool to flash twrp and then just install a rooted rom from twrp. My concern is buying a phone with the OTA 2.20 UPDATE and not being able root. Cuz I forsure am not buying phone I can't install a debloated rom on buy so long as I can get a custom recovery image I should be fine.
Sent from my Skyrocket running AOKP 4.1.1 Jelly Beeeaannsss
Click to expand...
Click to collapse
As far I know that u need to be rooted, with unlocked bootloader to be able to have recovery install.. U can try to root it and unlock the bootloader for 30 days right using old method before u can return the phone if you get 2.20 version instead of 1.85. But I believe someone would be able to crack it soon as well
Swyped from T3DroICS BlueICESense
ted77usa said:
Yes u can.....
I Got Used To That Option As well.....but U should check on Official Twrp Site Or Thread they The One made the recovery...maybe on their next Update they would add it that option....
As far I know that u need to be rooted, with unlocked bootloader to be able to have recovery install.. U can try to root it and unlock the bootloader for 30 days right using old method before u can return the phone if you get 2.20 version instead of 1.85. But I believe someone would be able to crack it soon as well
Swyped from T3DroICS BlueICESense
Click to expand...
Click to collapse
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
'fastboot.exe' is not recognized as an internal or external command,
operable program or batch file.
'fastboot.exe' is not recognized as an internal or external command,
operable program or batch file.
'fastboot.exe' is not recognized as an internal or external command,
operable program or batch file.
This is what I get when I run this
BIGDADDYXXL said:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
'fastboot.exe' is not recognized as an internal or external command,
operable program or batch file.
'fastboot.exe' is not recognized as an internal or external command,
operable program or batch file.
'fastboot.exe' is not recognized as an internal or external command,
operable program or batch file.
This is what I get when I run this
Click to expand...
Click to collapse
Try to re-download the file again u might have a bad downloaded...and then extract the zip file to desktop or folder> edit install.bat with NotePad ++ see what is the script are.....or I will check the link later on.....but it should say command like this .....if you use it for HoXatt ....fastboot.exe flash recovery openrecovery-twrp-2.2.0-evita.img
Swyped from T3DroICS BlueICESense
Hi all,
First of all, I have done tons of reading and searching the past 24 hours. I cannot find a definitive solution and really want to be sure not to brick my handset.
Handset is on OTA ICS
Here's what I did:
1) Downloaded official JB leak from the thread on XDA
2) installed RSD Lite 6.1
3) Installed Motorola Device Manager
4) plugged in my Telecom NZ Atrix 2 in fastboot mode
5) opened RSD
6) ran flash with the JB leak
Then I get "Flash Failed 1/14". Now my phone boots straight into fastboot. If I hold down both vol + pwr I can select normal boot and it's all ok. Cannot reset through Recovery as it shows !android then boots back to fastboot.
From the reading I've done, this is either the wrong firmware or a driver problem (I am on Win 8 but tried on a Win 7 machine too).
It looks like I now need to flash a correct fxz for my device. I'm a bit hesitant to try flash again in case I brick for good!
2 Questions:
Why won't the JB leak work on Telecom NZ handset?
Would it be ok to flash "6.7.2_EDEM-18-MEARET" from the ICS Firmwares Superthread?
Current system version:
672.1.20.MB865.TNZ.en.NZ
4.0.4
GAS_ASIA_EDISONICSTNZ_P015
Build:
6.7.2_EDEM-20
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
gilda311 said:
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
Click to expand...
Click to collapse
So, you're phone is AT&T, not international. You can't use Jelly Bean.
Thanks
gilda311 said:
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
Click to expand...
Click to collapse
Thanks so much. I'v been looking for something like this for hours, but this method is the first one that worked.
Rhys C said:
Thanks so much. I'v been looking for something like this for hours, but this method is the first one that worked.
Click to expand...
Click to collapse
Cool. Seems this will be helpful for NZ users
After a bit of playing around, I have come to the conclusion that RSDLite flashing will not work with Telecom NZ handsets. Next thing to investigate is if we can upgrade to JellyBean through a script like the above.
BTW, To get root I ran the 2nd file in this thread
gilda311 said:
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
Click to expand...
Click to collapse
Rhys C said:
Thanks so much. I'v been looking for something like this for hours, but this method is the first one that worked.
Click to expand...
Click to collapse
Yaaah, me too!
Many Thanks to gilda311 and alteredlikeness and jimbridgman. You saved me guys. Thank you soooo much! :laugh::good:
gilda311 said:
Cool. Seems this will be helpful for NZ users
After a bit of playing around, I have come to the conclusion that RSDLite flashing will not work with Telecom NZ handsets. Next thing to investigate is if we can upgrade to JellyBean through a script like the above.
BTW, To get root I ran the 2nd file in this thread
Click to expand...
Click to collapse
I have a kiwi A2 and I have successfully flashed through RSDLite every time I have used it. I've been on the JB leaks and ICS flashed with RSDLite with no issues. I think this problem occurs when the phone is flashed with a mismatched ctd file and is then tried to be overwritten again. I know it's no help for you guys now, but for all others with NZ phones, it's something to keep an eye out for.
I have a A2 from telecom, ive soft bricked my phone a lot of times and always been successful on fastbooting/RSDLite. I use a AT&T official firmware to RSDLite and once successful i root it, install bootstrap and restore nanroid backup to TelecomNZ's firmware. At the moment im running CM10(JB 4.1.2) flashed via CWM. I have never encountered any fail flashing. gilda, my system info is exactly the same as yours i guess im lucky to get a good a2.
JB TELECOM NZ flashing
gilda311 said:
OK... I figured out a fix
Using the script in this post I was able to restore to ICS by running the "restore to ics win" batch file inside the folder I downloaded of the 6.7.2_EDEM-18-MEARET.
Flashing with RSDLite would not work, I kept getting a cdt.bin error.
So, now I'm on OEM ICS (just not the Telecom NZ one)
Now to try get root!
Click to expand...
Click to collapse
Hi,
Thank you very much.. This helped me to restore back to ICS(MEARET) from the telecom NZ one after flash failure. Is there any batch file similar to the one used to restore back to ICS for Telecom NZ users to install JB on those mobiles? or any other way to install official JB leak? Thanks in advance.
msbaditya said:
Hi,
Thank you very much.. This helped me to restore back to ICS(MEARET) from the telecom NZ one after flash failure. Is there any batch file similar to the one used to restore back to ICS for Telecom NZ users to install JB on those mobiles? or any other way to install official JB leak? Thanks in advance.
Click to expand...
Click to collapse
The issue seems to be with RSD itsself. Maybe we could edit the 'restore-to-ics.bat' script to flash the JB firmware instead? I'm not particularly keen to be my own test subject but I REALLY want to try CM10 and MIUI... If I'm feeling adventurous tonight I'll give it a crack and post the results :good:
MGinshe said:
The issue seems to be with RSD itsself. Maybe we could edit the 'restore-to-ics.bat' script to flash the JB firmware instead? I'm not particularly keen to be my own test subject but I REALLY want to try CM10 and MIUI... If I'm feeling adventurous tonight I'll give it a crack and post the results :good:
Click to expand...
Click to collapse
All CM10/CM10.1 based ROMs and variants can be flashed on the stock ICS kernel. Most, if not all, of them actually REQUIRE you to be on ICS before flashing including the version of MIUI found here:
http://forum.xda-developers.com/showthread.php?t=2259993
There's no need to take the risk of modifying or attempting to modify the restore-to-ics.bat script just to flash those ROMs. You just need root, Boot Menu Manager, and a little knowhow and you'll be good to go.:thumbup:
Brought to you by time and relative dimensions in space.
There is a way to install stock jb on at&t atrix2, but cant get camera working!
Telecom NZ JB
MGinshe said:
The issue seems to be with RSD itsself. Maybe we could edit the 'restore-to-ics.bat' script to flash the JB firmware instead? I'm not particularly keen to be my own test subject but I REALLY want to try CM10 and MIUI... If I'm feeling adventurous tonight I'll give it a crack and post the results :good:
Click to expand...
Click to collapse
Thanks for replying, and as was quoted by u.. issue was not only with RSD.. over writing cdt fails during running that "restore-to-ics.bat" script and displays " INFO: PRE FLASH VALIDATION FAILURE". but flashing doesnt stop and skips that cdt file and proceeds to next step. Hopefully u will crack that and help many Telecom NZ usere like me. Thanks again
Downgrading
Hi,
I had the same problem. RDSLite fails on cdt.bin flashing
Seems that the problem is that RDSLite will NOT downgrade your device.
Telecom NZ OTA version is 6.7.2_EDEM-20
The fxz available online is 6.7.2_EDEM-18
This fails.
AT&T fxz is later version, and it works fine in RDSlite
Regards
Dejan
gilda311 said:
Hi all,
First of all, I have done tons of reading and searching the past 24 hours. I cannot find a definitive solution and really want to be sure not to brick my handset.
Handset is on OTA ICS
Here's what I did:
1) Downloaded official JB leak from the thread on XDA
2) installed RSD Lite 6.1
3) Installed Motorola Device Manager
4) plugged in my Telecom NZ Atrix 2 in fastboot mode
5) opened RSD
6) ran flash with the JB leak
Then I get "Flash Failed 1/14". Now my phone boots straight into fastboot. If I hold down both vol + pwr I can select normal boot and it's all ok. Cannot reset through Recovery as it shows !android then boots back to fastboot.
From the reading I've done, this is either the wrong firmware or a driver problem (I am on Win 8 but tried on a Win 7 machine too).
It looks like I now need to flash a correct fxz for my device. I'm a bit hesitant to try flash again in case I brick for good!
2 Questions:
Why won't the JB leak work on Telecom NZ handset?
Would it be ok to flash "6.7.2_EDEM-18-MEARET" from the ICS Firmwares Superthread?
Current system version:
672.1.20.MB865.TNZ.en.NZ
4.0.4
GAS_ASIA_EDISONICSTNZ_P015
Build:
6.7.2_EDEM-20
Click to expand...
Click to collapse
dejannk said:
Hi,
I had the same problem. RDSLite fails on cdt.bin flashing
Seems that the problem is that RDSLite will NOT downgrade your device.
Telecom NZ OTA version is 6.7.2_EDEM-20
The fxz available online is 6.7.2_EDEM-18
This fails.
AT&T fxz is later version, and it works fine in RDSlite
Regards
Dejan
Click to expand...
Click to collapse
Do you mean to say this which is available in firmware superthread? "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip".
Does RSDLite flashing of Telecom NZ OTA "6.7.2_EDEM-20" also works ?
I used sbf.droid-developers.org/edison/list.php source for fxz.
There's no 6.7.2_20, only _18. That might be the leak before the final OTA.
If you can find 6.7.2_20, that should work, or use AT&T one. That worked fine on my bricked telecom mobile:
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
msbaditya said:
Do you mean to say this which is available in firmware superthread? "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip".
Does RSDLite flashing of Telecom NZ OTA "6.7.2_EDEM-20" also works ?
Click to expand...
Click to collapse
Currently designed for the Wifi version only. Alternates available upon request.
This package includes the de-odexed system and framework folder based on a wifi model.
This is NOT a full install, so do NOT wipe before using.
This package is designed to be used with the custom recovery image. This will NOT work with Odin.
This will delete the current system and framework folders and flash the new ones in their place. This is only a temporary solution until a full rooted install is established.
De-Odexed Install Pack
Custom Recovery Image
Custom Kernel Packages
twistedumbrella said:
Currently designed for the Wifi version only. Alternates available upon request.[/url]
Click to expand...
Click to collapse
Request!
My Verizon GC120 should be here in a couple of days. As far as I know it is untouched stock. Let me know the commands to pull the files you need for this and the other dev work you are doing.
Thank you for taking the time to do the work! We all appreciate it!
Finally received a GC120 camera I can do something with. Attached are the .img files pulled. About says my phone is on 4.1.2 (LK3) but I keep getting an install update request although the folder titled as the update in /cache is empty (so there's nothing I can pull from that).
I also pulled the modem.bin but it says invalid file when I try to upload.
*These are the files for LK3
Camera updated to LL2. Updated files attached.
MC4 files attached
So maybe I screwed myself updating all the way to MK4 update. Can't root using framaroot now like I did with all the others. Gonna try a few other options.
Can someone please tell me the adb command to find whether a bootloader is locked or not? I have tried several I've found online and don't receive anything conclusive. Thanks.
Be back in a week or so. Final project is in the beta test stage so I am swamped until it reaches the release candidate.
twistedumbrella said:
Be back in a week or so. Final project is in the beta test stage so I am swamped until it reaches the release candidate.
Click to expand...
Click to collapse
can you upload samsung galaxy camera apk
Can anyone post efs.img? I've screwed up my Cam and i need to flash efs.img to mmcblk03. Was playing around with swap and screwed up!
BUMP!!!!
rudie_techie said:
BUMP!!!!
Click to expand...
Click to collapse
? It wasn't part of the system image and you didn't specify which model but even so, I doubt people are randomly checking this thread for who needs backups of radio partitions.
Its a EK-GC100 bootloader mode says EK-GC100_EUR_XX
rudie_techie said:
Its a EK-GC100 bootloader mode says EK-GC100_EUR_XX
Click to expand...
Click to collapse
I dug through everything I have but no efs.img and if I remember right, you'd need one with your IMEI. Best bet is probably a factory reset.
Didn't help... tried factory reset with stock recovery and cwm recovery... nothing helps... i don't know a way to get it fixed... will keep looking...
Finally got it fixed. As GC100 is similar to S3, downloaded efs file for S3 flashed it via odin through bootloader and voila... attaching the file for reference if anyone else gets into trouble!
rudie_techie said:
Finally got it fixed. As GC100 is similar to S3, downloaded efs file for S3 flashed it via odin through bootloader and voila... attaching the file for reference if anyone else gets into trouble!
Click to expand...
Click to collapse
It's usually easier to post it all in one thread and link to it instead of making the same posts in two threads and ending up with the same answers.
can someone please re upload or send me links in private message? I have dropbox, please I need it... my ****z bricked gotta fix it
damn can someone upload these links or the stock odin tar???
GC120_GC120VRAMH2_1366980_REV00_user_low_ship.tar.md5
?? ANYONE please.... help
Update: the patch for the latest OTA can be found here: http://forum.xda-developers.com/droid-turbo/general/enable-su4tl-49-stock-tethering-to-t3380911
Even though it's been reported that the old version works with the SU4TL-49 OTA, I recommend flashing the updated patch with the OTA, since the patch flashes a modified build.prop file, and the new patch will include any changes made to the build.prop by the OTA update.
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.
pastorbennett said:
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.
Click to expand...
Click to collapse
Flashed this to my Turbo yesterday; works like a charm. Thanks!
Guys, I'm sure this is dumbest question ever asked on XDA, but would somebody give me a hand on how to flash this via TWRP? I put the extracted files on my phone but couldn't find them to install from within TWRP, probably because they're not an .apk - do I need to somehow make these part of a ROM and flash the whole thing?
Just did sunshine/update/TWRP/root and everything is working great, if that makes any difference.
Thanks a lot!
thetastycat said:
Guys, I'm sure this is dumbest question ever asked on XDA, but would somebody give me a hand on how to flash this via TWRP? I put the extracted files on my phone but couldn't find them to install from within TWRP, probably because they're not an .apk - do I need to somehow make these part of a ROM and flash the whole thing?
Just did sunshine/update/TWRP/root and everything is working great, if that makes any difference.
Thanks a lot!
Click to expand...
Click to collapse
With TWRP you do not flash the extracted files. You flash the zip. It has to be a "flashable" zip, but this one is.
Over in the bootloader unlock warning image thread, some people were trying to flash a zipped file that was not meant to be flashed. The image was meant to be unzipped/extracted and then flashed with ADB.
But in this case this is a TWRP flashable zip.
Worked perfectly! Thank you both so much - this is a lifesaver!!
pastorbennett said:
This is exactly what the thread title says. The zip replaces the stock build.prop file with one modified to enable native tethering. This is not guaranteed to work with any other build than SU4TL-44. I have personally tested this on my own phone. If you use this on any other build, you do so at your own peril.
Flash in TWRP.
And a quick apology, I had thought I was in the General section when I started the new thread. If any moderators want to move this to the General section, by all means, please do.
Click to expand...
Click to collapse
Worked as advertised. I still have unlimited data and racked up an impressive 180GB of data. What a life saver!
Anyone tried this with the latest OTA yet?
Jazzy Josh said:
Anyone tried this with the latest OTA yet?
Click to expand...
Click to collapse
It works just fine.
Jazzy Josh said:
Anyone tried this with the latest OTA yet?
Click to expand...
Click to collapse
KOAO said:
It works just fine.
Click to expand...
Click to collapse
It works with the latest OTA? That's good to know. I hadn't tried, since the patch basically overwrites the stock build.prop, and there's always going to be a few changes in the file whenever a new update is installed.
I did put together a patch for the latest OTA, which I would recommend flashing if you used the SU4TL-44 version, as the build.prop file reports the software version to the OS.
The thread for that patch is here:
http://forum.xda-developers.com/droid-turbo/general/enable-su4tl-49-stock-tethering-to-t3380911
Sent from my XT1254 using XDA-Developers mobile app