Related
Hey all.
On the Verizon i815 tab we seem to have a modem and a separate LTE modem. In the OTA files the scripts always do a
write_firmware_image("/tmp/modem.bin")
and the LTE file gets pushed to /dev/block/mmcblk0p8.
Now the question is, WHERE does the write_firmware_image call flash the bin file and how can I extract it from a running and updated device?
Background: We have one user who by some weird coincidence got the ICS OTA update pushed from Verizon. Everyone else's update always fails (whole debacle can be found in different threads). We now managed to have this one user pull a clone copy of all of his partitions via dd if=/dev/block/mmcblk0pxx of=/sdcard/file_xx commands and pushing those into another tablet yields a working ICS with updated LTE modem but the "regular" baseband still shows the old version!!!
I need to know how this one successfully updated user can dump his modem.bin and where we need to flash this dd or using this proprietary write_firmware_image function, so that in the end everything is updated as if the OTA had worked in the first place ...
THANKS
Pershoot is the king with the 10.1 tab variants, maybe he he can shed some light.
Sent from my SCH-I815 using xda premium
Most devices will store the CDMA modem.bin in the nvram so it unfortunately cannot be dumped like a normal partition.
Perhaps the kernel drivers could be modified to extract it, though I've never looked into such things very far.
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Most devices will store the CDMA modem.bin in the nvram so it unfortunately cannot be dumped like a normal partition.
Perhaps the kernel drivers could be modified to extract it, though I've never looked into such things very far.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
electron73 said:
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
Click to expand...
Click to collapse
This may be the first instance where Honeycomb is actually useful (the recovery part LOL)
electron73 said:
DAMN I kinda thought it would be something like this. Luckily I found a way to trick Verizon/Samsung's server to push the latest OTA to my tab where I was able to extract the needed modem.bin file. It's just a total pain in the behind, also because CWM can not flash the cdma part. For that we always need stock recovery and the latest stock recovery is of course locked, doesn't accept unsigned update files. *bastards* !!
Click to expand...
Click to collapse
Is the bootloader locked?
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Is the bootloader locked?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Yes of course. It's Verizon
electron73 said:
Yes of course. It's Verizon
Click to expand...
Click to collapse
Lame.
How were you guys using cwm then?
I may know of a solution even if the bootloaders are locked.
Sent from my SCH-I500 using xda app-developers app
jt1134 said:
Lame.
How were you guys using cwm then?
I may know of a solution even if the bootloaders are locked.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Well it seems like it's "half locked" then. The tab allows you to flash any recovery but nothing else. No kernel, no system fs. And they are locking it down further with every update. New ICS recovery won't flash unsigned zips anymore.
What solution do you have? Always interested in learning more about this stuff.
OK. I can probably help then. I'll post more details when I get home in a little bit.
Sent from my SCH-I500 using xda app-developers app
electron73 said:
New ICS recovery won't flash unsigned zips anymore.
Click to expand...
Click to collapse
Whoa...really? If we ever deliberately unroot, how would it ever be possible to restore it post-ICS? (I'm only aware of the recovery-injection method.)
Rodney
Oh Samsung....you never change...
Seems they're still using the same type of bootstrap initramfs as they have been for years. This allows unpacking and repacking of a kernel image
Linked below is a copy of the ICS recovery.img that has been repacked with the following changes:
* start adbd as root by default
* recovery keys replaced with 'test' keys
If this boots it should allow access to stock recovery with adbd, and should allow the stock recovery to flash unsigned zip packages. If so, you may create a zip package that can flash modem deltas (or tits).
DISCLAIMER: I don't even have this device, so I haven't tested anything. I came by this forum for other reasons. If it doesn't work or breaks something, then well, have a beer or something (though I see no reason it will break things even if it does not work as intended).
http://www.mediafire.com/?wnbr1v846yldl94
Flash with Odin or Heimdall, or whatever you folks are using for such things.
rhester72 said:
Whoa...really? If we ever deliberately unroot, how would it ever be possible to restore it post-ICS? (I'm only aware of the recovery-injection method.)
Rodney
Click to expand...
Click to collapse
It seems you can simply ODIN your CWM back on and then take it from there. As long as they don't close that hole at some point... Right now with the latest ICS version, even with stock recovery installed, this is still possible.
jt1134 said:
Oh Samsung....you never change...
Seems they're still using the same type of bootstrap initramfs as they have been for years. This allows unpacking and repacking of a kernel image
Linked below is a copy of the ICS recovery.img that has been repacked with the following changes:
* start adbd as root by default
* recovery keys replaced with 'test' keys
If this boots it should allow access to stock recovery with adbd, and should allow the stock recovery to flash unsigned zip packages. If so, you may create a zip package that can flash modem deltas (or tits).
DISCLAIMER: I don't even have this device, so I haven't tested anything. I came by this forum for other reasons. If it doesn't work or breaks something, then well, have a beer or something (though I see no reason it will break things even if it does not work as intended).
http://www.mediafire.com/?wnbr1v846yldl94
Flash with Odin or Heimdall, or whatever you folks are using for such things.
Click to expand...
Click to collapse
Awesome! Thanks for your help. Now of course I have a few questions and hope you can give me a quick rundown.
how do I unpack this img. I have linux and good knowledge of linux and unix tools. You say it's an initramfs? Is there a tutorial somewhere that explains how to unpack, modify and repack such a thing? And where do I make the changes if I were to do it myself with *our* ICS recovery?
I believe I can't just flash this one as there are big differences between the international versions and our LTE version of the Tab 7.7
The partition table is different etc. I don't want to use this and end up screwing my stuff up. I'd rather take the original one that came with our ROM and modify it myself.
You don't happen to also know how to unlock the bootloader so that we could just flash a rom with ODIN ?
The recovery I posted is a modified version of the one that asenduk posted in the other ICS thread. When I get to a PC later I'll post a link to the tools that I used to modify it. Its pretty straightforward.
As far as unlocking the bootloader, that's above my pay grade. Perhaps kexec would be a useful thing to look into?
Sent from my SCH-I500 using xda app-developers app
I think maybe we could start a donation for Mr JT to get the i815?
If he's interested yeah?
He's done many marvelous things!!
repack scripts : https://github.com/project-voodoo/kernel_repack_utils
toolchain : http://www.codesourcery.com/public/...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
use extracter.sh to unpack the image into a folder, edit to taste, then use repacker.sh to put it back together.
make sure to use gzip compression when repacking.
jt1134 said:
The recovery I posted is a modified version of the one that asenduk posted in the other ICS thread. When I get to a PC later I'll post a link to the tools that I used to modify it. Its pretty straightforward.
As far as unlocking the bootloader, that's above my pay grade. Perhaps kexec would be a useful thing to look into?
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
You say it has a locked bootloader, but we have CM10 which uses a custom kernel...
okashira said:
You say it has a locked bootloader, but we have CM10 which uses a custom kernel...
Click to expand...
Click to collapse
Well... Bootloaders I have never really looked into.. I am still unable to flash a kernel or a factory fs with ODIN. Odin only lets me flash the recovery. So something is locked there. Maybe not crazy-locked like the motorola razr phones but also not completely open like the AT&T Galaxy Note was... Maybe someone with a little more experience in this stuff can shed some light
jt1134 said:
repack scripts : https://github.com/project-voodoo/kernel_repack_utils
toolchain : http://www.codesourcery.com/public/...-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
use extracter.sh to unpack the image into a folder, edit to taste, then use repacker.sh to put it back together.
make sure to use gzip compression when repacking.
Click to expand...
Click to collapse
Cool! Thanks for the links. Will look at the stuff and see if I can figure it out
Just installed the Google Wallet installer on my Nexus 4 as i am rooted and the wallet no longer works. However, after doing so the phone hangs at a black screen after displaying the Google logo, it moves no further. I can access Clockwork Recovery and i've factory reset the entire thing but it still hangs after the Google logo. any suggestions? i'm trying to install a stock rom but i cant get the rom onto the sd card. I can't seem to get 'install zip from sideload' to work either..
Any suggestions?
Any help would be greatly appreciated!
maybe install factory image found in one of the nexus 4 root kits and start again
Sent from my Nexus 4 using xda app-developers app
There is a download link for stock images in the "Return to stock" thread stickied in general. Grab system.img and use fastboot to flash it.
fastboot flash system system.img
port76 said:
maybe install factory image found in one of the nexus 4 root kits and start again
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Okay so just done this and i still receive the black screen after the google logo. whats the possibility that its bricked?
port76 said:
maybe install factory image found in one of the nexus 4 root kits and start again
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
estallings15 said:
There is a download link for stock images in the "Return to stock" thread stickied in general. Grab system.img and use fastboot to flash it.
fastboot flash system system.img
Click to expand...
Click to collapse
i apologize but i can't seem to find the image file youre referring to. might you be able to link me directly to it? i appreciate your help
If you are seeing the Google logo you aren't bricked. Someone will be able to link you to the stock .img files and you have to flash them through fastboot.
joshnichols189 said:
If you are seeing the Google logo you aren't bricked. Someone will be able to link you to the stock .img files and you have to flash them through fastboot.
Click to expand...
Click to collapse
excellent thank you!
CAN SOMEONE PLEASE LINK ME TO THE SYSTEM.IMG?!
olsywolsy said:
i apologize but i can't seem to find the image file youre referring to. might you be able to link me directly to it? i appreciate your help
Click to expand...
Click to collapse
I can't believe I'm helping anyone who uses "HALP!" but here.
https://docs.google.com/file/d/0B_zuNWpIf1ujNlFDVnZ3dzg2WEU/preview?pli=1
estallings15 said:
I can't believe I'm helping anyone who uses "HALP!" but here.
https://docs.google.com/file/d/0B_zuNWpIf1ujNlFDVnZ3dzg2WEU/preview?pli=1
Click to expand...
Click to collapse
ah come on, we're all friends here. I believe thats what ive been doing for the past hour or so but sadly to no avail, its just a black screen again after flashing the stock rom. any other suggestions?
i followed the guide shown here: http://forum.xda-developers.com/showthread.php?t=2010312&page=2 and i'm currently hanging at the google logo.
If you flashed bootloader.img, boot.img and system.img and it still doesn't work, then.....?
Bad download?
Bump
estallings15 said:
If you flashed bootloader.img, boot.img and system.img and it still doesn't work, then.....?
Bad download?
Click to expand...
Click to collapse
well i dont think so, ive downloaded the file multiple times and nothing seems to change. can i just confirm the system.img file you were referring to is in fact titled "occam-jop40d-factory-ca7602f0.tgz" in the link you sent me?
Boot into stock recovery and factory reset.
olsywolsy said:
well i dont think so, ive downloaded the file multiple times and nothing seems to change. can i just confirm the system.img file you were referring to is in fact titled "occam-jop40d-factory-ca7602f0.tgz" in the link you sent me?
Click to expand...
Click to collapse
Are you unzipping it?
Yes I extracted the all but the zip, after doing that all became clear and I'm finally up and working. Thanks for your help!
Sent from my Nexus 4 using xda app-developers app
I am unable to update my rooted Nexus 7 with OTA 4.3 updates! I have stock ROM and stock Kernal.
I got the 4.3 notification update but when i select it my Nexus 7 reboots but instead of installing the updates it takes me to the TWRP recovery! I even tried using the install option and selected the update downloaded in the cache folder but it didnt install!
All i want is to update to 4.3 without losing my data
Please help! Thanks
Most likely you / an app modified something on your /boot and/or your /system partition and so one of the asserts is failing during the update process. I would suggest to do the update manually with the factory image. In my blog (a link you can find in my signature) I described, how to do it without loosing data.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Most likely you / an app modified something on your /boot and/or your /system partition and so one of the asserts is failing during the update process. I would suggest to do the update manually with the factory image. In my blog (a link you can find in my signature) I described, how to do it without loosing data.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
There are a lot of assumptions in your tutorial, like for instance, that everyone knows what to type those commands into or an easy way to copy the files to the sdcard to keep the root.
A literal step by step would be nice.
teeth_03 said:
There are a lot of assumptions in your tutorial, like for instance, that everyone knows what to type those commands into or an easy way to copy the files to the sdcard to keep the root.
A literal step by step would be nice.
Click to expand...
Click to collapse
I suppose if someone is digging around with rooting and flashing he should know the basics, like fastboot and adb. If not, he should try to learn those things before modifying it. Everything someone needs to know is written here within the how-to's.
Sent from my Nexus 7 using xda app-developers app
To flash the bootloader do I need to be in recovery or Android... or bootloader?
ankushkool said:
I am unable to update my rooted Nexus 7 with OTA 4.3 updates! I have stock ROM and stock Kernal.
I got the 4.3 notification update but when i select it my Nexus 7 reboots but instead of installing the updates it takes me to the TWRP recovery! I even tried using the install option and selected the update downloaded in the cache folder but it didnt install!
All i want is to update to 4.3 without losing my data
Please help! Thanks
Click to expand...
Click to collapse
OTA updated can only be applied to complete stock system including stock recovery. You cannot flash OTA with TWRP. Either you can get a stock zip file that is TWRP compatible (check XDA general thread) or go back to complete stock and apply the update.
teeth_03 said:
There are a lot of assumptions in your tutorial, like for instance, that everyone knows what to type those commands into or an easy way to copy the files to the sdcard to keep the root.
A literal step by step would be nice.
Click to expand...
Click to collapse
I agree I know a little, but, many 'Senior' members, presume we have 'senior' knowledge, and OK about learning first, that's fine, but, if we already had this knowledge, we wouldn't be asking for help!
Please, realise, there are many, myself included that have limited knowledge, and ask for help, superior attitudes are of no use .........
Horse Trader said:
I agree I know a little, but, many 'Senior' members, presume we have 'senior' knowledge, and OK about learning first, that's fine, but, if we already had this knowledge, we wouldn't be asking for help!
Please, realise, there are many, myself included that have limited knowledge, and ask for help, superior attitudes are of no use .........
Click to expand...
Click to collapse
No, it's not that someone doesn't want to help, but nobody wants to write the same stuff again and again. Fastboot, adb, recovery, etc. are basics for rooting and flashing and there are already a lot of very useful tutorials dealing with these topics. So why not collecting all those useful information and putting it together ...
I was able to flash stock 4.3 which wiped my data (I planned on this happening) and rooted it again to use stick mount.
The problem is when 4.2.2 came out, I was able to update with the OTA even though I was rooted, can't remember how, but I'm pretty sure I did. I had used the toolkit which makes things simple for everything, you basically just plug the Nexus in and hit a few buttons on your keyboard to unlock and root.
Well, because of the rooting, 4.3 does not currently work with OTA, so it actually required some know how to do.
The point I'm trying to make here, is that if you are going to write a tutorial, its good to be thorough. If you don't like writing the same thing over and over, write a Getting Started page, and link it every time you write a guide that needs drivers installed and fastboot/adb tools downloaded.
Its not hard to do what I did for any stretch of imagination, but it takes a bit of googling and referencing multiple sources to get anything done because of all the assumptions that are made around here. Its pointless to write a half of a guide, because the people that understand it don't need to read it because they probably already figured it out on their own.
You are free to ignore my "tutorial", but, sorry, I will not Google around on behalf of other people because they probably might have a lack of knowledge to understand my postings.
AndDiSa said:
Most likely you / an app modified something on your /boot and/or your /system partition and so one of the asserts is failing during the update process. I would suggest to do the update manually with the factory image. In my blog (a link you can find in my signature) I described, how to do it without loosing data.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info, got mine updated without losing any data :good:
I just need a tester for a small idea i have for installing twrp recovery and 2nd bootloader in a safer manner than usual. The other manners are pretty safe but i figured this seemed really safe because its so simplistic in nature. I don't know whether i will continue this project depending on the results of the test, but basically i thought why not make a 2nd init/bootstrapped twrp that runs a ota update on a zip file that just installs everything for you with a conveniently placed zip file with asserts that it checks for then deletes itself. My first test is just for a 2012 kfhd 7" that either has no 2nd bootloader + twrp and a fastboot cable handy to restore in case this soft bricks it or one with a version of twrp already installed that it higher than 2.6.0.0. I don't wanna post the actual file because i don't want accidental bricks. Chances are based on how this works it will probably brick the first time around because i have not messed with the hijack scripts to mount everything properly yet, but this was taken from another omap based device so if it doesn't work i don't think it will take too much tweaking, but the initial binary it tries to run may cause some havok. I can assure you this should be easy to restore from in twrp by simply renaming a system file, otherwise without a copy of twrp already installed you will have to restore with kffa. I need the kindle that this is being tested on to also be on a rooted amazon os, not another rom. I have no idea if twrp will work with amazon's stock kernel so this should be interesting. post back if you are interested.
If you are wondering why i didn't decide to test this on my own first its simply because i don't feel like having to wipe my entire data partition and restore the data from my pc just to clear selinux xattribs off my data partition so that amazon's kernel will not throw a fit.
So overview for those that don't want to read that big paragraph:
Requirements:
-Running Amazon OS with root
-Have a way to recover from brick (2nd bootloader + twrp or flash back with kffa/srt) - twrp preferred but plz have a never version than 2.6.0.0 installed.
-Have busybox installed
stunts513 said:
I just need a tester for a small idea i have for installing twrp recovery and 2nd bootloader in a safer manner than usual. The other manners are pretty safe but i figured this seemed really safe because its so simplistic in nature. I don't know whether i will continue this project depending on the results of the test, but basically i thought why not make a 2nd init/bootstrapped twrp that runs a ota update on a zip file that just installs everything for you with a conveniently placed zip file with asserts that it checks for then deletes itself. My first test is just for a 2012 kfhd 7" that either has no 2nd bootloader + twrp and a fastboot cable handy to restore in case this soft bricks it or one with a version of twrp already installed that it higher than 2.6.0.0. I don't wanna post the actual file because i don't want accidental bricks. Chances are based on how this works it will probably brick the first time around because i have not messed with the hijack scripts to mount everything properly yet, but this was taken from another omap based device so if it doesn't work i don't think it will take too much tweaking, but the initial binary it tries to run may cause some havok. I can assure you this should be easy to restore from in twrp by simply renaming a system file, otherwise without a copy of twrp already installed you will have to restore with kffa. I need the kindle that this is being tested on to also be on a rooted amazon os, not another rom. I have no idea if twrp will work with amazon's stock kernel so this should be interesting. post back if you are interested.
If you are wondering why i didn't decide to test this on my own first its simply because i don't feel like having to wipe my entire data partition and restore the data from my pc just to clear selinux xattribs off my data partition so that amazon's kernel will not throw a fit.
So overview for those that don't want to read that big paragraph:
Requirements:
-Running Amazon OS with root
-Have a way to recover from brick (2nd bootloader + twrp or flash back with kffa/srt) - twrp preferred but plz have a never version than 2.6.0.0 installed.
-Have busybox installed
Click to expand...
Click to collapse
If I can get my Kindle back up and running, I'll have a go at it for you. But that's a pretty big if right now.
Sent from my iPod touch using Tapatalk, somewhere in the time vortex
Ok thanks, kinda surprised no one has offered before you. This had over 100 views. I guess not too many people are using amazon os that are willing to risk a softbrick. Hopefully this will work I think it is a bit safer than the other methods for beginners that don't want to risk anything.
Tapatalk is annoying me to no end lately... Had to type this message again because quick reply is being glitchy.
Sent from my Amazon Tate using Tapatalk
I could also volunteer. I have an extra Kindle fire 7" Hd. It is rooted and running 7.4.8. I have my trusty fastboot cable and I already have system images for a quick restore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
The safest method is to "fastboot -i 0x1949 flash bootloader oldbootloader.bin" then "fastboot -i 0x1949 reboot" (assuming you're using the cable and it auto-kicks you into bootloader mode again) "fastboot -i 0x1949 flash recovery twrp.img" and finally "fastboot -i 0x1949 oem recovery"
Edit: This is a more complex version of Hashcode's method, posted on the cm11 installation instructions page.
Sent from my Nexus 7 using Tapatalk
Yea but the thing about that method is sometimes people have bad downloads and don't check for md5sums(not to mention tons of people always having driver issues). If everything is in a signed zip file then if the signature verification fails its about the same as a bad md5sum, not to mention I can add a md5sum comparison in the update-tools script. I was just wanting to make a one click bootloader install option that comes from an apk, kinda like fire flash but simpler.
Sent from my Amazon Tate using Tapatalk
So you're suggesting using an OpenRecoveryScript to flash twrp, the old bootloader, and apply the stack override file to allow for that "2nd boot loader" hack?
Theoretically, that should work, but Amazon might have put restrictions on the recovery to only allow Amazon-signed zip files so that something like this couldn't happen.
Sent from my Nexus 7 using Tapatalk
I thought only Amazon's recovery would have issues with the signature, even if tarp does I can just disable the signature check and use the update-script to check the md5sum before flashing.
Sent from my LG-P769 using Tapatalk
stunts513 said:
I thought only Amazon's recovery would have issues with the signature, even if tarp does I can just disable the signature check and use the update-script to check the md5sum before flashing.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
If TWRP is required, doesn't that make this pointless, because you need the 2nd bootloader hack to make twrp work in the first place? Or perhaps I'm just misunderstanding...
EDIT: when I have the time, I'll see if I can manage to recover from my weird semi-brick and if so, I'll revert to stock and help you test.
Sent from my Nexus 7 using Tapatalk
Thanks, and what I,m saying is you run twrp through 2nd init. I have done it on my phone before, has the same hardware as a kf1 with twice as much ram. I have not seen tarp implemented in this manner before though, only cwm, that's another reason I wanted to test this idea.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Thanks, and what I,m saying is you run twrp through 2nd init. I have done it on my phone before, has the same hardware as a kf1 with twice as much ram. I have not seen tarp implemented in this manner before though, only cwm, that's another reason I wanted to test this idea.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Oh. You mean a FakeFlash? That's when you flash a zip that actually just overlays a second recovery. Ex. Flashing a TWRP FakeFlash would allow you to use TWRP from the stock recovery without replacing the installed recovery.
Sent from my Nexus 7 using Tapatalk
r3pwn said:
Oh. You mean a FakeFlash? That's when you flash a zip that actually just overlays a second recovery. Ex. Flashing a TWRP FakeFlash would allow you to use TWRP from the stock recovery without replacing the installed recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That kinda sounds like it, for a more detailed explanation, this is what i'm basing it off of: http://forum.xda-developers.com/showthread.php?t=2095825
I believe thats the right link. Had to search for it so it might not be but i think it is.
stunts513 said:
That kinda sounds like it, for a more detailed explanation, this is what i'm basing it off of: http://forum.xda-developers.com/showthread.php?t=2095825
I believe thats the right link. Had to search for it so it might not be but i think it is.
Click to expand...
Click to collapse
Kindle's back up and running, I'll test it.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ok I'll upload it tomorrow. I was just checking my notifications. On a side note I left my kindle in the car and woke and woke up and realized it, having to use my phone to check messages because I will cause a domino reaction if I open the front door... it starts with dogs waking up...
Sent from my LG-P769 using Tapatalk
Sorry I haven't uploaded it yet, i will upload it when I have a chance, my weekend has been chaotic because I've been having to prepare for the job I am starting training for tomorrow. I have been meaning to do it but I hit another snag when I finally got some time to myself I told Ubuntu to upgrade to 14.04 and then unity surprised me and now apparently can't set the window buttons to right so I feel like i'm using a mac which I do not like at all so I decided to use mate since its pretty much what mynfavorite Ubuntu distribution had 10.04lts) so I have been spending the better part of the day reconfiguring it so it was more so like Ubuntu 10.04's theme but I modernized it a bit. Still not done with the theme yet but it is much much better. I think I'm going to attempt to add transparency to the theme. Just realized how off topic i went. Anyways I will see about uploading it tomorrow after I get off of work.
Sent from my Amazon Tate using Tapatalk
Hey guys I'm fairly new to the droid, but not new to installing stuff and that. I've tried multiple times to install a recovery but twrp doesn't, through fast boot it says it's invalid or something. Somehow I got cwm on it but to install a new Rom I've to make a complete backup since I've heard these phones brick pretty easily. The data can't be mounted to backup And I can't backup on internal storage either.
If you guys could help me out a bit it would be great. Thanks
Sent from my XT907 using XDA Free mobile app
jafferkhan said:
Hey guys I'm fairly new to the droid, but not new to installing stuff and that. I've tried multiple times to install a recovery but twrp doesn't, through fast boot it says it's invalid or something. Somehow I got cwm on it but to install a new Rom I've to make a complete backup since I've heard these phones brick pretty easily. The data can't be mounted to backup And I can't backup on internal storage either.
If you guys could help me out a bit it would be great. Thanks
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Which system version are you on, and which version of TWRP did you try? Where did you get the TWRP? Check this thread it has all the walkthroughs and download links needed... Side note this should be in general or q&a not in the Dev section
We cannot teach people anything; we can only help them discover it within themselves.
I'm on the stock rom 4.4, and I've already gone through the steps, as I said and understand how these things work, the cwm I'm using now installed but doesn't allow for a data backup. I read there isn't one for this phone which allows that.
Sent from my XT907 using XDA Free mobile app
Which TWRP did you use... Where did you get it from.... Please check the linked thread and ensure you grabbed the proper TWRP for our device also maybe try flashing by a different method if you did use the correct TWRP
We cannot teach people anything; we can only help them discover it within themselves.
jafferkhan said:
I'm on the stock rom 4.4, and I've already gone through the steps, as I said and understand how these things work, the cwm I'm using now installed but doesn't allow for a data backup. I read there isn't one for this phone which allows that.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Actually I am also on 4.4 kk.. And also I tried a lot TWRP's they don't work! Idk why but just didn't open when click to recovery!
Also a lot of cwm's won't work. I only found one working recovery.
livecouk said:
Actually I am also on 4.4 kk.. And also I tried a lot TWRP's they don't work! Idk why but just didn't open when click to recovery!
Also a lot of cwm's won't work. I only found one working recovery.
Click to expand...
Click to collapse
i went through the suggested link again, decided to go with Twrp and used flashr from playstore to flash it. worked out great, now i've got a fully backed up stock 4.4
dbreezy187 said:
Which system version are you on, and which version of TWRP did you try? Where did you get the TWRP? Check this thread it has all the walkthroughs and download links needed... Side note this should be in general or q&a not in the Dev section
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
got it, thanks mate