I've noticed people saying to make sure your battery is fully charged when flashing the stock sbf. How long does this process usually take. Going to flash it back and root the new ota and I was wondering how long ill be off the grid for.
mudd_cat23 said:
I've noticed people saying to make sure your battery is fully charged when flashing the stock sbf. How long does this process usually take. Going to flash it back and root the new ota and I was wondering how long ill be off the grid for.
Click to expand...
Click to collapse
This is not a development question, and should be in the Q&A section.
It takes about 5-10 minutes. Having done the process about 35-40 times now, I have the entire flash 1.26, root, update to 1.57, reroot process down to about 20 minutes.
Well, for me, I have a really fast core i5 Sony Vaio, but I can't flash any phones with it because I always get errors (something not working right on Win7) so I have to use my old 2006 Sony Vaio with first gen core 2 duo (Centrino Duo) on XP. And with that said, it takes about 45 minutes on that POS.
So the speed of it is really all in the power of your computer.
amd quad core with win7 takes about 10 min
BravoMotorola said:
Well, for me, I have a really fast core i5 Sony Vaio, but I can't flash any phones with it because I always get errors (something not working right on Win7) so I have to use my old 2006 Sony Vaio with first gen core 2 duo (Centrino Duo) on XP. And with that said, it takes about 45 minutes on that POS.
So the speed of it is really all in the power of your computer.
Click to expand...
Click to collapse
You know that you may need to shorten the file name length; you call name it what ever you want, just don't have any space in the name or change the .sbf file extension. Also, a good idea to make sure the file path doesn't have spaces in it as well; just put the .sbf in the root c:\
Swiftks said:
You know that you may need to shorten the file name length; you call name it what ever you want, just don't have any space in the name or change the .sbf file extension. Also, a good idea to make sure the file path doesn't have spaces in it as well; just put the .sbf in the root c:\
Click to expand...
Click to collapse
Do this.
I have an i7 with 8 cores and 8 GB of RAM running Windows 7...it's not your processor, it's RSD. Doing this worked for me.
I use my netbook with 2gb ram and its crappy little 1.nothing ghz processor atom processor and it only takes about 10 minutes
Sent from my MB860 using XDA Premium App
the time it takes to flash the default spf has nothing to do with your computers speed. ie cpu ram blah blah.
the person that says it is taking 45 minutes has a pc with usb 1.1 not usb 2.0
that is why it is slow.
on any normal pc expect 5-15 mins.
It took me about 10-20 minutes on the atrix both times.
hey i am not sure where to post this but i kinda did in mutiple posts ..after using RSD lite and toke the .sbf file.. it says failed flashing process and giving me the (0x7100). i dont know how to get out of "starting RSD protocol support"
I am kinda PANICKING RIGHT NOW!! I AM SCARED WHETHER MY PHONE IS BRICKED!
please help me out!! much appreciated!
takes me 14 minutes 27 seconds (yes I timed it) to flash 1.2.6, root, and update on a 3ghz amd quad with 8gb, and I have no problems with rsd with the file anywhere and any name length
ymmv, as with any software, I would be concerned if a single flash took more than 20 minutes though
Problem:
anirudh15891 said:
hey i am not sure where to post this but i kinda did in mutiple posts ..after using RSD lite and toke the .sbf file.. it says failed flashing process and giving me the (0x7100). i dont know how to get out of "starting RSD protocol support"
I am kinda PANICKING RIGHT NOW!! I AM SCARED WHETHER MY PHONE IS BRICKED!
please help me out!! much appreciated!
Click to expand...
Click to collapse
Possible Answer:
Swiftks said:
You know that you may need to shorten the file name length; you call name it what ever you want, just don't have any space in the name or change the .sbf file extension. Also, a good idea to make sure the file path doesn't have spaces in it as well; just put the .sbf in the root c:\
Click to expand...
Click to collapse
Swiftks said:
You know that you may need to shorten the file name length; you call name it what ever you want, just don't have any space in the name or change the .sbf file extension. Also, a good idea to make sure the file path doesn't have spaces in it as well; just put the .sbf in the root c:\
Click to expand...
Click to collapse
Yes, I do that. You see, shortening the file name only makes the 'start' button to where I can click it (where it's not grayed out). When I try to start it it gives me an instant error which I've looked up several time but cannot find the solution to. I had some old Motorola phone (like the ZN5) I used to mod, and flash with SBFs, and those would go through fine. It's weird, and I still don't understand why I get this error.
Related
Hello there,
I wanted to use the ShellTool I found at the FTP. But, after executing the file, I get an error, followed by opening a profile from friendster.com . After that, my Symantec AV is trying to search for the installation files and other strange stuff. When I give the computer a reboot, my computer tells me that NTLDR is missing. So, this file is some kind of windows wrecker instead of a usefull tool.
Not only the NTLDR was missing, also HAL.dll, ntoskrnl.exe and other files.
I tested it also on a virtual machine with Windows XP SP2, and the same thing happened. Please remove that kind of crap.
Its in the directory: Uploads/WIZARD/Unlocking/
i have had no problems at all...on vista ultimate and windows xp on a virtual machine and i flash with this tool...it works like a charm on my side...a charmmmmmmmm
i had the same thing happen to me, I had to re-install windows on two different computers after it crashed the,, pretty weak, pretty weak
someone deleted the original file and changed to a wrecker one.. owner please check the file if its your original or altered one by someone..
I'm going to have to say that someone removed the original ShellTool file and replaced it with the current one.
I downloaded the original file and have used it without any problems to flash several devices. So, don't go blaming the developer of this tool. There have been SEVERAL corrupted/virus-laden files uploaded to that folder recently.
The general rule of thumb on downloading from the ftp is to wait until the files have been checked by the admins and mods and moved to the "safe haven" and to NOT download anything from the "Uploads" section. Downloading from the "Uploads" directory is done at YOUR OWN RISK. (There are SEVERAL threads on the forums about this.)
BTW -- if you had read the entire thread in the G4 forum about the ShellTool, you would have known ahead of time about the virus-infected file. That discussion start with post #285 in the thread. http://forum.xda-developers.com/showthread.php?t=293480&page=29
We seem to be plagued by virii at the moment. :-(
If you look in the G4 forum (as I remember it) and find the original thread for ShellTool you will see later on virus warnings and some MD5 checksums for the original.
I'm going to write a thread this weekend on MD5ing files you publish and how users verify them.
Got it
OK. I've just deleted the Shelltool_bufixed.zip and replaced with the uninfected Shelltool_bugfixed in a RAR archive. I know that since I haven't posted before, but believe me that there is no virus on this one. Atleast, not at the time of me uploading it. (Don't know what people will do with it later)
Unfortunately I read this thread too late... I had my NTDLR deleted by this proggy. Might be a virus, might not be one... What makes me suspect its not is that it bypassed my corporate AV.
I recovered from the "virus" almost instantly (I dont know if it was posted or not, but I think it wont hurt anyone to read this):
1- Run the WinXP SP2 (if u have SP2 already installed) and AFTER you get to the license agreement, select REPAIR.
2- Use the recovery console google it or go here =) http://www.webtree.ca/windowsxp/repair_xp.htm
So much for Norton Corporate AV with all the latest updates bells and whistles
Cheers!
Candanga said:
Unfortunately I read this thread too late... I had my NTDLR deleted by this proggy. Might be a virus, might not be one... What makes me suspect its not is that it bypassed my corporate AV.http://www.webtree.ca/windowsxp/repair_xp.htm
(...)
So much for Norton Corporate AV with all the latest updates bells and whistles
Cheers!
Click to expand...
Click to collapse
There is nothing a AV can do (even the most powerful and expensive) to avoid infection by a 'cooked-in-5-minutes' malicious file.
In order to detect the file its signature/characteristics must be added to the scan engine and that will only happen after someone gets 'infected' and reports the fact
Anyone with a little skill can make an executable to delete system files and upload it to the ftp. That's why i prefer to post files in threads instead in ftp server; at least the previous can't be changed except by the poster or by mods/admins
cheers
Wanna kill u'r XP..?? Ask me how...
ftp://[email protected]/Upload/ShellTool_VIRUSFREE_beaware.zip
TRUELY IS A TOTAL XP KILLER!!!! I KNOW, AN EXPERIENCE IS UNADVISEABLE (GRANDMA, U R ABSOLUTELY TRUE) ,THOUGH IF U DON'T BELIEVE AND WANNA TRY, JUST SAVE ALL YOUR DATA FROM THE SYSTEM DRIVE BEFORE U HIT IT.... (and as far as my experience goes, huge amount of people spare their most important and intimate data on the system drive with no backup...and they cry)...AND GET READY AT LEAST EITHER FOR ANOTHER SYSTEM INNOVATION OR EVEN NICE AND CLEAN INSTALLATION.
THATS ALL
I don't get it, why should you guys use ShellTools, when you can already CID Unlock your G4 using HardSPL ?! That way you can flash you wizard in about 6 minutes vs the 30 minutes on ShellTools!
Technical sense, it is not a virus. The person who made this is lame enough to just make a BAT-EXE conversion which, delete stuff from your WINDOWS directory only. So, most of your stuff are generally safe (that's the common one that I've know appearing randomly in the FTP).
I have problems unzipping the file anyway, so I cant confirm this. If you are sure it is a fault, just delete it. Thanks.
dferreira said:
I don't get it, why should you guys use ShellTools, when you can already CID Unlock your G4 using HardSPL ?! That way you can flash you wizard in about 6 minutes vs the 30 minutes on ShellTools!
Click to expand...
Click to collapse
Sheeltools is safer for inexperienced. You can never brick the phone by it. You do not need to check the safety of ROM (since shelltool will never flash anything else than OS).
Faking unlocking the CID by SoftSPL/HardSPL is quicker, but it enables to flash IPL/SPL which is not a good idea (newbie eagerness or just a stupid oversight of somebody who flashes daily can lead to disaster).
There are cases of people who bricked their Wizards by using SoftSPL without reading properly (for example I remember one Polish guy not so long ago).
I use shelltools. It gives me peace of mind when flashing.
(Changing a genuine program for a malicous one can be done regardless of what program it is. So this has nothing to do with shelltools. Just be careful what you run on your computer).
Mirek
0. Make sure phone is hard-spl first
1. Make sure SD card is formatted with fat-32
2. rename the image file (ruu_signed.nbh) to rhodimg.nbh, then copy that to the ROOT OF THE MICRO SD CARD, Insert card into phone
3. Set your phone in bootloader (Hold the "volume down" and hold the power on button until you see the tri-color screen.
4. Then follow the on-screen instruction
5. (OPTIONAL) -after flash, make sure to hardreset (pull battery, insert battery then hold green and red PHONE buttons (send/end) and hold powerbutton) follow onscreen instruction.
thanks for the info
I've tried the above and somehow it won't work on my TP2, it stays at "Serial" text in the white box, I'm assuming it already went past the SD slot then? Checking for the image.
I have the Energy rom loaded on the SD card, named as explained in the first post in this topic, it is placed in the root of the SD card, no folders or other files exist on that card. I removed the SIM card from the phone just to be sure. Is there anything I am missing, or is there anyone else who actually used this method to flash his or her device?
Info:
SPL: OliNex 0.85
ROM: |RHOD|6.5|ROM|WWE| ★ EnergyROM "Warhawk" (23016) ★ | Built Aug 21 |Manila 2.5 / 2.1|
SD Card: 4GB MicroSDHC (No brand on card, supplied with the branded T-Mo TP2 (Vario V)
Formatted: fat-32
Thanks
The nbh file needs to be in capital letters! RHODIMG.nbh
And step 5 isnt to be done until the "Tap screen to set up device" screen!
Just reset when your phone says Update successful!
And done, name changed to the correct format. No luck. Reformatting the card now to see if that changes anything. Update in a few.
And that too didn't work sadly. Either someone here notices I'm doing something wrong, or I'll just wait till I get near a machine natively running Windows Running Mac OS here so can't run the executable, and read that it's not quite a good idea to flash it from a virtual OS.
PositiveCreep said:
And done, name changed to the correct format. No luck. Reformatting the card now to see if that changes anything. Update in a few.
And that too didn't work sadly. Either someone here notices I'm doing something wrong, or I'll just wait till I get near a machine natively running Windows Running Mac OS here so can't run the executable, and read that it's not quite a good idea to flash it from a virtual OS.
Click to expand...
Click to collapse
You will want to partition your card so the nbh image is in a partion of at the largest 1G, anything larger makes it hard for the phone to find and read the nbh file! I have a 1G card just for flashing and it works perfect! And it also may be the mac, they never play nice with windows!
It's not the mac screwing it up in this case as I am using a virtual Windows OS to work on the card. (MacOS leaves some folders on the card that I don't want on it)
Will try partitioning the card, cheers. I'll update when I know more. ANd thanks for the help ^_^
Update:
Partioned the MicroSD card to 0.5GB, no change sadly.
thanks for information
Ok, SD update worked now, however, step 5 won't go (Oh crap...) Have the grey screen with "Update Complete" and "UPDATE SUCCESS" However, it won't do anything if I hold down Send/End/Power at the same time for over 10 seconds. How long should that take normally? What's my best option right now? Can't see any other than to unplug the phone and take out the battary, however, will this brick it?
PositiveCreep said:
Ok, SD update worked now, however, step 5 won't go (Oh crap...) Have the grey screen with "Update Complete" and "UPDATE SUCCESS" However, it won't do anything if I hold down Send/End/Power at the same time for over 10 seconds. How long should that take normally? What's my best option right now? Can't see any other than to unplug the phone and take out the battary, however, will this brick it?
Click to expand...
Click to collapse
When is says "UPDATE SUCCESS", just rest with the stylus.
Dave
Thanks for the swift reply! Done it, it's booting up as I am typing this. Didn't quite have the guts to just do that without having read I could when flashing from SD. (Was unsure how the device would react to soft reset then a first booth with the SD present etc)
Anyways, rambling. Thanks!
these post are telling me how to flash while the rom is already on the phone, but i'm missing the step on how to get the rom file on the phone in order to move it to the sd card.......... how do i get the file to the phone? do i put it onto the phone from the computer or do i go to my browser on my phone and download it from there to the phone
htctpII said:
these post are telling me how to flash while the rom is already on the phone, but i'm missing the step on how to get the rom file on the phone in order to move it to the sd card.......... how do i get the file to the phone? do i put it onto the phone from the computer or do i go to my browser on my phone and download it from there to the phone
Click to expand...
Click to collapse
Everything you need to know is HERE. I really suggest you fully read the instructions so you avoid bricking your phone by mistake.
In re: making sure you're hardspl'd first, does that still apply if you're flashing an official ROM? Or just for user cooked ROMs?
I'm about to update my Verizon TP2 with the newly released official 6.5 from verizon. I'm not hard spl'd, and honestly, know very little about that particular modification.
not for official
I dont think you have to be hard SPL'd for an official ROM. I think everything is included in the ROM package. (at least for T-Mobile it is)
btw the .nbh does not have to be named in all capitals. I have personally done it both ways with no problems at all. RHODIMG.nbh works just as well as rhodimg.nbh
kwambewright said:
I dont think you have to be hard SPL'd for an official ROM. I think everything is included in the ROM package. (at least for T-Mobile it is)
Click to expand...
Click to collapse
Thanks for the quick response!
Sadly, the way the install file is set up to work, I can't get to the nbh file. It insists on installing that via an active sync connection. I was hoping it would extract from the exe and schedule it for active sync installation, then I could hunt down the ROM, copy it to my SD card, and run it from there.
fortunz said:
Thanks for the quick response!
Sadly, the way the install file is set up to work, I can't get to the nbh file. It insists on installing that via an active sync connection. I was hoping it would extract from the exe and schedule it for active sync installation, then I could hunt down the ROM, copy it to my SD card, and run it from there.
Click to expand...
Click to collapse
hmm.. sorry for kicking this post, but you can unpack the exe-file with winrar. just grab the biggest file you can find (RUU_signed.nbh, and rename it to rhodimg.nbh), copy it to your root-folder (fast way for accessing bootloader is to also copy the "EnterBootLoader.exe" -file to your SD-card, and to start that file after copying both the files). Now just enter the bootloader, and it works! (don't be scared when the screen goes black for a moment, and the bootloader has reloaded. It's meant to do that )
I still have a little question by the way: is it possible to flash the hardSPL this way? or should i rename it to something else?
No, Hard SPL needs to be done from the PC as it checks IMEI online and IP address. You only get 1 licence, can ask for more or purchase more licences, but it can't be done any other way...
ultramag69 said:
No, Hard SPL needs to be done from the PC as it checks IMEI online and IP address. You only get 1 licence, can ask for more or purchase more licences, but it can't be done any other way...
Click to expand...
Click to collapse
Yeah, it's a pity this has been done (though I understand why...)
My device cannot connect to PC anymore, so cannot use HSPL anymore!
InjecTioN said:
hmm.. sorry for kicking this post, but you can unpack the exe-file with winrar. just grab the biggest file you can find (RUU_signed.nbh, and rename it to rhodimg.nbh), copy it to your root-folder (fast way for accessing bootloader is to also copy the "EnterBootLoader.exe" -file to your SD-card, and to start that file after copying both the files). Now just enter the bootloader, and it works! (don't be scared when the screen goes black for a moment, and the bootloader has reloaded. It's meant to do that )
Click to expand...
Click to collapse
Much obliged. I've actually been scared off the official vzw 6.5 because of issues upgraders have reported, but someday I'll put that to use.
Bad day today. Why? Because this morning I decided to try out one of the Eclair roms before leaving for work. I flashed it, tried it and then looked at the time. After noticing that I had only 15 minutes before having to be at work I decided that it was time to lock up my computer and take off... but first... I need to restore back to a stable rom. So I restarted my phone and using switchrom I recieved an error of some kind. Not a big deal because anytime I flash a new rom I do a switchrom -s, bart backup AND nandroid+ext backup. Then everyday I use a bat script to automatically mount my sdcard and back it up to my pc just in case I need to format my card and restore everything later. Which brings me to the point of this thread. I was able to restore CM-4.2.8.1 but it was booting VERY slowly (about 15 minutes) and I noticed that it still said "Checking for errors" in the status bar. I left my phone on the charger and checked it later and it said that my sdcard was damaged. I have absolutely NO computer access and my phone is running WAAAYYYY to sluggish to use. So I just turned it off and put my sim in my old Tilt phone and used that for the day.
So... throughout the ENTIRE day I was going through Android withdrawls. I needed my G1. It was killing me.
So my question/idea is, is there a way to do a chkdsk on the fat partition of from the recovery menu or from terminal? I did a little searching and came up with something called dosfsck. And I looked in the /system/bin/ directory and saw something called fsck_msdos. Can we use this to repair the errors that the system finds on the sdcard? If the OS can scan and detect errors, then why can't we have an option to fix them? Instead of having to use a computer at home or the office.
Any thoughts? Thanks.
Binary100100 said:
I was no longer the Hero.I needed my hero. I needed to be rescued.Times were changing people changed, things got hard for me .
Any thoughts to rescue my savior ???
Click to expand...
Click to collapse
The thing is that is part of the windows OS, i know cause i use it to check for errors on my HDD or SD cards time-time. Im not sure if linux or distro or whatever its called has that feature avail.
Oh and i had that prob before where it was devastatingly sluggish.
Ace42 said:
The thing is that is part of the windows OS, i know cause i use it to check for errors on my HDD or SD cards time-time. Im not sure if linux or distro or whatever its called has that feature avail.
Oh and i had that prob before where it was devastatingly sluggish.
Click to expand...
Click to collapse
Uhhhh... is that a paraphrased version of what I said in the quote? LOL.
Here... I found this: http://linux.die.net/man/8/fsck.vfat
I don't see why it can't be implimented somehow into a recovery.img to avoid future problems. It'll basically be like e2fsck but for fat.
Binary100100 said:
Uhhhh... is that a paraphrased version of what I said in the quote? LOL.
Here... I found this: http://linux.die.net/man/8/fsck.vfat
I don't see why it can't be implimented somehow into a recovery.img to avoid future problems. It'll basically be like e2fsck but for fat.
Click to expand...
Click to collapse
Oops sorry about that, didnt think anyone would notice.
Maybe you should check that up with Amon_RA?
I usually use my SD reader to check for errors before i flash a rom.
Ace42 said:
Oops sorry about that, didnt think anyone would notice.
Maybe you should check that up with Amon_RA?
I usually use my SD reader to check for errors before i flash a rom.
Click to expand...
Click to collapse
Yeah I guess I'll do just that.
I did find this too:
http://www.netmite.com/android/mydroid/donut/external/dosfstools/doc/README.dosfsck
So it looks like someone had the idea already. I wonder why it's never been implemented.
Binary100100 said:
Yeah I guess I'll do just that.
I did find this too:
http://www.netmite.com/android/mydroid/donut/external/dosfstools/doc/README.dosfsck
So it looks like someone had the idea already. I wonder why it's never been implemented.
Click to expand...
Click to collapse
The fat32 probably does get corrupted, sometimes i get the sd isnt inserted error.
Ace42 said:
The fat32 probably does get corrupted, sometimes i get the sd isnt inserted error.
Click to expand...
Click to collapse
I never get that but whatever is wrong with my sdcard it must be major because my pc is still trying to recover it after an hour later.
Binary100100 said:
I never get that but whatever is wrong with my sdcard it must be major because my pc is still trying to recover it after an hour later.
Click to expand...
Click to collapse
Copy the files to your pc, then erase the partition via console.Then do the error check again. I think its having trouble since you have a lot of files on your sd that must be zip or maybe you have a .img
Ace42 said:
Copy the files to your pc, then erase the partition via console.Then do the error check again. I think its having trouble since you have a lot of files on your sd that must be zip or maybe you have a .img
Click to expand...
Click to collapse
I think it was Vista. I never should have used the error check option in the disk properties menu. I just tried it again using dos (chkdsk f: /R) so it actually tells me what it's doing. The error checking tool in vista is just like the defrag tool. You have absolutely no idea what's going on or how much longer it's going to take. Sucks.
Binary100100 said:
I think it was Vista. I never should have used the error check option in the disk properties menu. I just tried it again using dos (chkdsk f: /R) so it actually tells me what it's doing. The error checking tool in vista is just like the defrag tool. You have absolutely no idea what's going on or how much longer it's going to take. Sucks.
Click to expand...
Click to collapse
I upgraded to 7
But i did like vista because of the HW support and eye-candy. I do wonder what its checking while it does that though.
Interestingly enough (I don't know the reasons), it looks like Motorola left a copy of Nvflash and Atrix-specific bootloader.bin for it on the Atrix. What's interesting about Nvflash is that it allows for targeted backup and restore of partitions (i.e. something along the lines of what Nandroid allows for, except at a lower level), which decreases recovery time when developers do something that ends up soft-bricking their phone. It should also break us free of our dependence on SBFs because we'll be able to create our own backups.
Anyways, the Nvflash on the phone is the Linux i386 binary. The bootloader.bin isn't platform specific, as it's meant for the target, rather than the host. THe archive is available in /usr/local/share/motorola/fireboxmake/OSH_tools.tgz.
Unfortunately, this is where we get stuck, because we don't currently know how to get a connection to the phone. And that's where all of you come in! Can you get further? I've gotten this far:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
I imagine that some of the functionality may end up requiring the --sbk flag (and we don't know the SBK right now), but I'm hoping that we can at least backup and restore /system, /data, and /osh.
Update: Information I've obtained indicates that this is the error you get when the SBK you pass in doesn't match the SBK on the system. So, no luck until we get that SBK.
Update 2: Additional links from dasmoover:
Tegra crypto engine source snapshot
/osh/usr/local/share/motorola/fireboxmake
Credit to dasmoover for the find.
Correct me if I'm wrong but isn't this the same thing as which apparently folks are trying to get taken down in the name of keeping the info under wraps?
I would like to excuse myself for earlier. I am glad that you have turned this in to something positive.
Sent from my MB860 using XDA Premium App
JdeFalconr said:
Correct me if I'm wrong but isn't this the same thing as some other thread, which apparently folks are trying to get taken down in the name of keeping the info under wraps?
Click to expand...
Click to collapse
It's related, but it's not quite the same thing. If nothing else, you have the binaries for this right now on your phone (dasmoover posted a link on the IRC channel 12 hours ago or so). I'm at this mostly for the backup/restore capabilities of Nvflash rather than bootloader hacking. Even if we only ever had that much, I'd be thrilled, because I hate having to re-SBF and set everything up again every time I soft brick my phone.
Also: I've been planning on posting this for a few hours now, before that other post even went up. I'm... disappointed to see that other post, but these two things aren't after the same thing.
http://gititbit.ch/fbm1 - /osh/usr/local/share/motorola/fireboxmake
also contains OSH_tools.tgz.
Firebox is the development name for the Webtop system. This contains the tools to prep the partition image for flashing. There are also some files IDA generated.
May be of use: http://gititbit.ch/tces1 - Tegra Crypto Engine Source Snapshot
do you mind me asking but.. what was that other thread about that it warranted getting deleted.
seven2099 said:
do you mind me asking but.. what was that other thread about that it warranted getting deleted.
Click to expand...
Click to collapse
it got deleted for a reason - let it be
I think we are getting warmer now .......... this calls for some investigation.
minooch said:
it got deleted for a reason - let it be
Click to expand...
Click to collapse
Wow he was just asking a questing...If you feel that even just telling him/us what the thread was about is so bad/dangerous then i think there is a bigger problem here. This should be a place to share information, ideas and if we start cracking down on that then we lose so much (yes if it is copyrighted or under nda then take it down)
http://forum.tegratab.com/viewtopic.php?f=13&t=18
They've been using nvflash to flash their tablet.
Perhaps someone can pull their SBK right out of the phone
sys/fuse/SecureBootKey
I doubt it is of any use because once pulled from the phone it appears as 0 bytes.
Looking at it from the phone shows nothing.
my guess is, as the path describes, a fuse, once lit, makes the file blank.
I navigated to nvflash with root explorer and executived the file. All get is executing file and nothing. I figured this would be.the case. Where would this need to run? A recovery state?
Sent from my MB860 using XDA App
sifon187 said:
I navigated to nvflash with root explorer and executived the file. All get is executing file and nothing. I figured this would be.the case. Where would this need to run? A recovery state?
Click to expand...
Click to collapse
The recovery state would be similar to the RSD recovery state (set on boot by pressing Volume Down) except that there's a specific Nvflash one. But, that's the one I can't get to respond properly.
LOOK HERE
LOOK HERE
http://forum.xda-developers.com/showthread.php?p=13145274#post13145274
blackax said:
Wow he was just asking a questing...If you feel that even just telling him/us what the thread was about is so bad/dangerous then i think there is a bigger problem here. This should be a place to share information, ideas and if we start cracking down on that then we lose so much (yes if it is copyrighted or under nda then take it down)
Click to expand...
Click to collapse
there is a separate dev forum that we can't access for DEVs only that that information is being used on. it being in the open here might hurt our chances of being able to exploit anything as moto might find it and patch it before the devs have a chance to get at it.
Is the Dev forum on XDA or.somewhere else just curious
Sent From My Gibgerblurred Phone
it's on xda, but you have to be a recognized developer of xda to access it.
PAulyhoffman said:
Perhaps someone can pull their SBK right out of the phone
sys/fuse/SecureBootKey
I doubt it is of any use because once pulled from the phone it appears as 0 bytes.
Looking at it from the phone shows nothing.
my guess is, as the path describes, a fuse, once lit, makes the file blank.
Click to expand...
Click to collapse
I am a complete noob and not close to a dev but if pulling the file blanks it the why not view the file while still on the phone while using an external source or application? Again like I said noob so sorry if alreay tried
thats just my 2 cents
sent from XDA mobile
Wow give a dime at least...
Sent from my MB860 using XDA App
drock212 said:
I am a complete noob and not close to a dev but if pulling the file blanks it the why not view the file while still on the phone while using an external source or application? Again like I said noob so sorry if alreay tried
Click to expand...
Click to collapse
Ends up being the same thing. Running sudo cat on the file prints nothing. That was one of the first things tried, even before copying the file.
I'm trying to use my laptop to edit a file that's on my phone's storage. Every time I open the file, I am told that the files location is write-protected (so, read-only). I can move the file to my computer to edit it that way, but how would I remove this limit anyway?
Download to PC, edit, upload back to phone is what I do. Most times I edit them on the phone though. Pretty much my 10+ is my laptop.
That thrill never seems to get old.
blackhawk said:
Download to PC, edit, upload back to phone is what I do. Most times I edit them on the phone though. Pretty much my 10+ is my laptop.
That thrill never seems to get old.
Click to expand...
Click to collapse
Okay...so back to my question...
How would I remove the write protection so I can edit the file without having to copy the file around?
Snowka85 said:
Okay...so back to my question...
How would I remove the write protection so I can edit the file without having to copy the file around?
Click to expand...
Click to collapse
Root, ADB?
I don't think that's a normal functionality.
I have 2 work arounds so I don't concern myself with it as my phone spends very little time connected to the PC.
It's all and only backup time at this point.