Related
Hi everyone, if you are having trouble with upgrading the ROM on the US TG01, then this is your topic! Here are the few things you must do the update the ROM:
-Fully charge your battery
-Format your MicroSD card to FAT32, then create a folder called "prg" (don't type the speech marks), and place your ROM in there, and don't forget to change it's extension to .enc from .tsw
-Remove the black tab under the SIM slot, beware, pull it upward, not forward
-Can you see the three "yellow circles" on the SIM slot? The first and third one are what we wanted the connet together. Link/connect them with a wire
-Push the power button for 10 seconds
-Wait a little bit
Done!
Don't thank me, thank leeston for all his continous support, hey, thank you again man!
El Diablo said:
Hi everyone, I've just tried with the mirolg's Sense included English ROM to upgrade the software version on my TG01, but it's just restarting, so nothing changes, any ideas?
Click to expand...
Click to collapse
Not enough detail for me to help you. Please reply to the following.
1. Which method did you use, short pin or sddl+?
2."just restarting", do you mean that the sd downloader doesn't start and goes straight to Toshiba screen or it starts then resets the device making no changes?
3.If the sd downloader starts, does it say 'Variant Invalid' briefly before it restarts?
If you dont know what shortpin or sddl+ means then look HERE.
Sorry, I did not informed you very well,
I've used the sddl+ method. Clicking on the sddl+ restarts the device, just like a soft reset. If I click on the SD downloader, then it says "Invalid filename".
Thanks for the reply.
Now the SD Downloader says "Error occurred during system reset" when I click Download.
Err?
I'm wondering, is that too difficult to help a mate who is having a problem? PLEASE???
El Diablo said:
I'm wondering, is that too difficult to help a mate who is having a problem? PLEASE???
Click to expand...
Click to collapse
I assume you've read the sticky about rom flashing and are still having problems, follow the guide below and let me know how it went.
Download my ROM from HERE.
Download 7Zip from HERE.
Download sddl+ from HERE.
1.Install 7Zip
2.Right click "TG01WP_StonromR7.7z" and choose "7Zip -> Extract to "TG01WP_StonromR7.7z\"" (This will create a folder called "TG01WP_StonromR7" in the same place as the downloaded file)
3.UnRAR sddl+
4.On your storage card create a folder named "prg" (no speech marks)
5.Copy "TG01WP_Stonrom.tsw" to the "prg" folder on your storage card.
6.Copy sddl+ to the root of your storage card. (root = not in a folder, just straight on the card)
7.Open file explorer and go to your storage card and open sddl+
8.You will now have a white screen, with the text "sd downloader - do not remove battery or storage card" (it may not say exactly this, i can't remember just now)
9.Wait
10.Wait a bit more
11. The phone should restart after a bit of waiting, the first boot can take a long time. Be patient.
I only say use my rom because i know it flashes and boots on my 2 devices.
If this doesn't work, pay attention to the on screen messages during flashing and post them here word for word, along with which rom you tried and any other info that you can provide.
Thanks again for your help, downloading right now, I'll inform you about the process.
It doesn't work, only says "Invalid filename" if I click on the TG01_SDDL.
If I click on the tg01_sddl+, the device just restarts, no further changes, still the same problem.
???
BTW, I changed the ROM's name to TG01WP_00.tsw, now the SD Downloader says "Error occurred during system reset".
El Diablo said:
It doesn't work, only says "Invalid filename" if I click on the TG01_SDDL.
If I click on the tg01_sddl+, the device just restarts, no further changes, still the same problem.
???
BTW, I changed the ROM's name to TG01WP_00.tsw, now the SD Downloader says "Error occurred during system reset".
Click to expand...
Click to collapse
Only thing i can think of is to rename the .tsw to .enc.
I tried that too. It doesn't work neither.
BUT,
Thank you very, very much for your afford.
Post edited, detailed informations added.
Have you tried updating you TG with the manufacturer update instead of a cooked ROM? Just to prove that flashing is possible on your device.
I would suggest using the official update and SD Downloader from Toshiba.
Please post back with your experiences.
Yes, actually I've tried with the TG01WP-WM6.5-UK file. Result: Same
El Diablo said:
Yes, actually I've tried with the TG01WP-WM6.5-UK file. Result: Same
Click to expand...
Click to collapse
Where did you get the file? The correct file name should be "TG01WP_5005000176.tsw" or "TG01WP_5005000167.tsw" not "TG01WP-WM6.5-UK"
Just to clarify, is it an Orange UK TG01? Did you buy it from a shop or second hand?
I got the file from Toshiba's official web site (Europe).
Err, I don't know where my device is from, but I can assume you it's a TG01, not the "A" one.
Here, the file is included on the file I've downloaded:
TG01WP_5005000176.enc
Ok, the phone is from USA, I guess it has a different software version updater.
El Diablo said:
Ok, the phone is from USA, I guess it has a different software version updater.
Click to expand...
Click to collapse
The only thing i can see that is left now is to use the short pin method. Details are in the guide to flashing tut in the sickies. You will need to make sure the radio versions are the same first though.
Start\settings\system\about\version info. Where it says radio version is what you need to know. Mine is "5005.1600.05" so would be referred to as 1600 here. If you let me know what radio you have i will upload a ROM with the correct radio for you.
This may take me a little while though.
Radio version is 5001.0000.5319
Very different, heh?
El Diablo said:
Radio version is 5001.0000.5319
Very different, heh?
Click to expand...
Click to collapse
I'll try and find a rom with that radio, for now though try renaming the tsw to .enc and try short pin.
I think some phones released to America have different radio hardware than UK phones. I'm not sure if this is the case for the TG01 though. I think we have a few American forum users. Maybe they could help if they are reading this?
Anyway, I really appreciate your help and support.
Hi folks, i'm looking for 2 days a way to solve my DHD problem:
It can't boot anymore. It pop up the "htc quietly brilliant" screen, play the boot sound and, start this step again, and again, and again...
So I'm googling a LOT about how to solve this, if exist a way to restore the original rom. Because i'm thinking that was the problem, my original rom is gone.
That happens when i try to install 3 softwares from appbrain, my device got freeze and i hit the power button to reset. So, after that, my device is gone.
So i came here, to ask you folks: There is a way to recover the original rom ? Without send to warranty (because it spend something like 1 month here).
I'm not a mobile hacker or something, i'm just trying to be happy with my device.
Thanks a lot and sorry for my poor english!!
Perhaps try booting to the bootloader, by holding Power + Volume down button. From there, you should be able to do a factory reset, which may or may not fix your problem. Worth a shot at least, imo
And if it does not work when you do a factory reset, you can use a rom.zip from HTC RUU to restore your phone.
Now the important thing is to know which HTC rom you are running. If it is unbranded, 1.72.405.3 is a sure shot. Download the RUU.exe from Stock roms thread in android development subforum, and run it. When the window pops up, open run prompt, and type: "%TEMP%". Then search for rom.zip, copy it to your desktop, rename it to PD98IMG.zip and put it to your SD card (I hope that you have a card reader). Then just reboot to bootloader as tmh described, and watch the magic happen
Then if your phone is branded, you can still use the same technique to make PD98IMG.zip, but you have to get the RUU that matches your branding. There are lots of RUUs in android development subforum, just search.
Hi guys,
thanks a lot for quik reply!
I perform the procedure indicated by tmh, but without lucky ;\
I think it is unbranded. I buy it at Portugal and i'm using at Brazil right now.
I'll perform your tip jkoljo.
I'll post a repply to let people know if it works or not.
Thanks a lot!!
Hope the advice the last guy gave helps , a factory re set may work fine and fix the issue. Iv had 3 dhd since the day of release , the second one I had wouldn't switch on, had it replaced by Vodafone . Not sure weather or not they will give you a new one . Hope u get it fixed
Sent from my Desire HD using XDA App
I'm not sure if i got cover from warranty.
Right now, my "PROOF OF PURCHASE" is at europe, and i'm at america, so i must get this work again by myself, or pay (some expensive value, i think) for htc support.
I found those ROM version:
RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe 04-Jan-2011 12:41 285M Windows executable file
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
but i'm not sure about "WWE". What it means?
dogasantos said:
I'm not sure if i got cover from warranty.
Right now, my "PROOF OF PURCHASE" is at europe, and i'm at america, so i must get this work again by myself, or pay (some expensive value, i think) for htc support.
I found those ROM version:
RUU_Ace_HTC_WWE_1.72.405.3_R2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163262_signed.exe 04-Jan-2011 12:41 285M Windows executable file
RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed.exe
but i'm not sure about "WWE". What it means?
Click to expand...
Click to collapse
the different is just the radio version. just try flash one of them and see if that work.
WWE means World Wide English, which is an international release
Any one of those RUUs you linked is ok, as hedayat7 already said.
WWE is World wide English...so both are english Roms...try the RUU flash, it should work like a dream....
jkoljo said:
Download the RUU.exe from Stock roms thread in android development subforum, and run it.
Click to expand...
Click to collapse
Sorry ask for your help again, but at Official thread (thread number 841207) for DHD files, both 1.72.405.3 links are broken.
So i search for another thread, and found another one, but when i run the .exe, it ask for a USB connection to device, so it appears wrong.
Could you gimme a hand to find the correct file?
PS: I can help with a web hosting to all correct files.
You probably found the correct RUU, now proceed to %TEMP% and copy rom.zip to desktop.
You can find RUUs here: http://xdafil.es/index.php?path=DesireHD/RUU/
I am not completely sure if those zip files are actual rom.zips, you can check that. Open up the zip, and if it has a long list of hboot, system, android-info.txt etc, then it is rom.zip and you can just go ahead and rename it to PD98IMG.zip.
jkoljo said:
You probably found the correct RUU, now proceed to %TEMP% and copy rom.zip to desktop.
You can find RUUs here: ...
I am not completely sure if those zip files are actual rom.zips, you can check that. Open up the zip, and if it has a long list of hboot, system, android-info.txt etc, then it is rom.zip and you can just go ahead and rename it to PD98IMG.zip.
Click to expand...
Click to collapse
But i did that.
The "1.72.405.3" files at this URL are broken (Or need password to access it, because "You don't have permission to access" message pop up).
When i run the RRU i got two screens, first i must accept a advice, the second one ask if I have a USB connection to my device. Even when i proceed to next step, i got no .zip file on my %TEMP%.
Im lost because of that lol
UPDATE: OK I FOUND IT! haha ty
Thanks a lot my friends,
but it doesn't work.
I perform the process for 2 different roms, and it doesn't work.
Still can't boot.
I'll sent for warranty and wait a loooong time..
But thanks a lot for help me with this!!
Ok, then there is something wrong in the device itself. You have to send it to a service center.
Sent from my Desire HD using Tapatalk
Hi again,
i keep a little hope that i can restore my phone, so i found a possible solution:
OTA update.
At "showthread.php?t=667728&page=2", i found a guy with the same problem i think, here is the quote:
Kinma said:
I had the same problem last week.
I suspected it had to do with the EXT3 partition.
Solved it by first flashing the OTA 2.2 ROM (for rooted users) as this does not use the EXT3. Then used Rom manager to recreate the EXT3.
Now all ROMs that use the EXT3 run fine!
Click to expand...
Click to collapse
(thanks Kinma for the feedback)
So, i start a search for OTA update file here, and found at "showthread.php?t=885996".
But when i choose "Apply sdcard:update.zip", i got INVALID OPERATION.
Someone have a tip for me about this?
Thanks (its very sad, but i must keep hope).
dogasantos said:
(thanks Kinma for the feedback)
Click to expand...
Click to collapse
You are welcome.
What happened was that after a reboot of the phone the phone started rebooting in the boot sequence, i.e. a boot loop.
I tried a lot of things and nothing worked.
Finally I suspected that the problem might be with the SD card. I had a backup, so I had no problem doing a factory reset.
Then I booted the phone without the SD card.
The phone booted fine.
That way I was certain that the problem was with the SD card.
I had 2 partitions on the SD card, an EXT3 part and the rest was a normal Fat part.
I could still read the card, so I made a backup of all the data on the card.
Then I reformatted the card using windows.
The phone booted fine with an empty, reformatted, SD card.
Since I use Apps 2 SD, I had to recreate the EXT3 partition.
If your rom does not use this, you do not have to do this.
After recreating the EXT partition, put back all files that I want on my SD card.
My advice would be to do a factory reset and after that boot the phone without the SD card.
If the phone boots, you know the problem is with the card.
Hope that helps; good luck!
dogasantos said:
Sorry ask for your help again, but at Official thread (thread number 841207) for DHD files, both 1.72.405.3 links are broken.
So i search for another thread, and found another one, but when i run the .exe, it ask for a USB connection to device, so it appears wrong.
Could you gimme a hand to find the correct file?
PS: I can help with a web hosting to all correct files.
Click to expand...
Click to collapse
Here, use this link:
http://forum.xda-developers.com/archive/index.php/t-899564.html
From "football" post copy and paste his link, the download would start immediately..
Hi folks,
boot without the SD card, doesn't work =(
I'm really without luck with this.
I do:
- Factory reset
- Clear cache and userdata
- Boot without SD or/and SIM cards
- Reflash RUU WWE 1.72.405.3 Radio 26.04.02.17_M2
- Reflash RRU WWE 1.72.405.3 Radio 26.04.02.17_M2 SF
- erase all SD
One show was use OTA update.zip, but at this step i got "invalid operation"
SO, nothing works!
Well, it appears a lost battle =\
thanks folks for all help.
Yeah, there must be something wrong in your device itself, for example a motherboard fault. Send it back to HTC.
yukinok25 said:
Here, use this link:
http://forum.xda-developers.com/archive/index.php/t-899564.html
From "football" post copy and paste his link, the download would start immediately..
Click to expand...
Click to collapse
Hi,
I found the information extremely useful. Big Thanks
GRuti
I wanted to do a full format to reload system and urukdroid. I went into recovery and formatted. All is format and I downloaded the new version from archos.com and put it into root. Pressed ok to disconnect usb and get the error Update failed1). Please help.
wow...36 views and no one has a reply. come on guys and girls
mallard6453 said:
I wanted to do a full format to reload system and urukdroid. I went into recovery and formatted. All is format and I downloaded the new version from archos.com and put it into root. Pressed ok to disconnect usb and get the error Update failed1). Please help.
Click to expand...
Click to collapse
You downloaded the normal firmware or sde from archos.com?
Why you just install the sde and urukdroid? You dont need the normal archos android, do you?
You downloaded the normal firmware or sde from archos.com?
Why you just install the sde and urukdroid? You dont need the normal archos android, do you?
Thank you so much. I was able to do it as you suggested. Just got some bugs to work out.
Thank you so much. I was able to do it as you suggested. Just got some bugs to work out.
Click to expand...
Click to collapse
No Problem
Tip:
There is a "Quote"-Button under each post, with that you dont need to copy and paste the questions above your post to directly answering it
I found my solution on another forum and it appeared that if there was a (1) or (2) etc in the firmware filename, the archos would not see it. I renamed the file taking the (1) out and low and behold it installed the latest firmware from archos.
mallard6453 said:
I found my solution on another forum and it appeared that if there was a (1) or (2) etc in the firmware filename, the archos would not see it. I renamed the file taking the (1) out and low and behold it installed the latest firmware from archos.
Click to expand...
Click to collapse
Aaah that was the problem
You've downloaded the aos file several times
Hi everyone, I've read every topic related but couldn't find any proper solution and couldn't post in development forum also I use linux on desktop but could be counted as a dummie for this stuff.
Here's the sory; Got new fresh nook, without reading any instruction backed up my Nook files via its usb connection as an img file. Then like an idiot, I've writed the nookie image to the NOOK's memory as it seems and got an error. After rebooting my Nook it became unstable in screen and started an error pop-up says:
"Your Nook encountered an error that need to restart
If this problem persists, please contact our Costumer Service."
Since not any core files deleted from my failed root try, just tried to format the drive as it seems 223MB; Nothing changed. What I did for recover is trying to boot up with an SDcard installed nookie devs. Nothing changed. Tried to recover from the back-up file which gave me the error of "Error#0 occured while writing to disk at sector 465792". I've tried to format it via partition wizard but still the same error. Also tried the solution of rosa87 introductions from his topic as it fail as everything else and decided to open a fresh new topic as the problem source is different. Also I'm out of U.S to contact any official technical service.
Any reccomendations?
P.S: I'm on windows machine runs 7.
Sphixxx said:
Since not any core files deleted from my failed root try
Click to expand...
Click to collapse
If you wrote the Noogie image onto your NST, then you did in fact overwrite core files.
You're also not the first one to do this mistake.
- At this point your NST could have been easily fixed by booting the n2T-Recovery v0.2 image.
Sphixxx said:
, just tried to format the drive as it seems 223MB;
Click to expand...
Click to collapse
Why on earth would you do that?
If you don't know what is going on, it sure aren't gonna help formatting parts of the internal flash.
- At this point your NST is much harder to repair, but maybe not entirely impossible.
Sphixxx said:
Nothing changed. What I did for recover is trying to boot up with an SDcard installed nookie devs.
Click to expand...
Click to collapse
This part I do not understand.
Sphixxx said:
Nothing changed. Tried to recover from the back-up file which gave me the error of "Error#0 occured while writing to disk at sector 465792".
Click to expand...
Click to collapse
How did you try to write it back? What tools? How big is your backup file?
Sphixxx said:
I've tried to format it via partition wizard but still the same error.
Click to expand...
Click to collapse
Again with the formatting? why?
Sphixxx said:
Also tried the solution of ros87 introductions from his topic as it fail as everything else..
Click to expand...
Click to collapse
Yes it would fail because you've deleted all the critical files needed to recover your NST.
Forgive me if I sound a bit harsh, I do no intend to, but you made things so much worse by starting to format things and I hope others who read this post and get into trouble later on remembers this and ask us for help before trying to fix it themselves
Check your PM in a few mins.
Restart Required Error
I too have this problem, but my NOOK's memory was corrupted.
I don't know what to do... n2T-Recovery 1 and 2 was failed.
Yes it would fail because you've deleted all the critical files needed to recover your NST. Forgive me if I sound a bit harsh, I do no intend to, but you made things so much worse by starting to format things and I hope others who read this post and get into trouble later on remembers this and ask us for help before trying to fix it themselves Check your PM in a few mins.
Click to expand...
Click to collapse
I was deleted the files, but I made a backup.
Help please!
Hi folks!
Just bought myself an S5, have successfully rooted the phone, and decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
I'm on android v4.4.2 - I backed up prior to this so I've just restored back to factory settings for the meantime, but I'd like to know why I'm getting those two errors if possible?
Many thanks!
ggiiaann91 said:
decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
Click to expand...
Click to collapse
Could be many reasons, you don't have enough information yet to know. Crucially, you failed to paste the verbatim error and the context surrounding it here. Or even link to the theme you refer to. So we don't have much to go on.
As it is labeled as an OTA theme, it will be specifically formatted for that custom ROM. So wouldn't it make more sense to seek help in the custom ROM support thread?
The actual error could be anything from a corrupt download (did you verify the md5 checksum or try downloading the theme again?) to a marginal USB cable (did you try a different USB cable and port?). Or many other things. Did you search the support thread to see if anyone else was troubleshooting similar issues?
.
Sorry, I'm completely new to the forum so don't know my way about.
How would I go about obtaining/providing the verbatim error?
ggiiaann91 said:
How would I go about obtaining/providing the verbatim error?
Click to expand...
Click to collapse
You can copy and what you see on screen from the log that Odin or Kies makes. Or alternately make a screenshot.
Most questions could be expediently answered by a search of the forum too. But for some reason, most people don't try that.
.
fffft said:
You can copy and what you see on screen from the log that Odin or Kies makes. Or alternately make a screenshot.
Most questions could be expediently answered by a search of the forum too. But for some reason, most people don't try that.
.
Click to expand...
Click to collapse
I appreciate that, I did try looking via the forum before asking but didn't find any mention of 'verbatim'...
I also searched for the errors I am experiencing and whilst I found several other threads, none are a similar scenario to mine.
I am not using Odin or Kies, I was able to root my phone successfully, and installed the Alliance Rom with no issues.
My issue occurs after downloading an the OTA update/theme and then going into recovery mode > Install Zip > Choose zip from /sdcard > OtaDownloads/ > Install Black_Glass_S5
I ticked to check the MD5 sum, it came back with with 'MD5 check: error'
Signature verification causes the 'E: footer is wrong and E: signature verification failed' errors.
ggiiaann91 said:
I did try looking via the forum before asking but didn't find any mention of 'verbatim'...
Click to expand...
Click to collapse
Your search technique needs polishing. If some particular keyword doesn't work in a search, then use a synonym or reword your search query.
ggiiaann91 said:
I ticked to check the MD5 sum, it came back with with 'MD5 check: error'
Signature verification causes the 'E: footer is wrong and E: signature verification failed' errors.
Click to expand...
Click to collapse
And there is crucial information that you didn't provide earlier. The very reason why I wanted the verbatim context. We are't psychic and can't help you effectively if you don't provide a detailed account.
Adding those details is a huge improvement. You selected a feature (check md5) without understanding how it worked. That caused an error. You then asked us what the error meant without telling us that you had done that and not providing any context or details for us to work with.
The error message, in context, tells us that you either tried to check md5 on a file that doesn't have a md5 - therefore a spurious error. Or the file was profoundly corrupt.
.
It's not my intention to be vague, I simply do not know what information is relevant/beneficial to you.
I deleted the file and then re-downloaded a new copy but it still won't unzip the file, the issue also occurs for another OTA file.
If there's specific info I can provide then by all means let me know and I'll provide it.
Appreciate the help and patience - evidently I'm still a noob when it comes to all the features/tools.
ggiiaann91 said:
If there's specific info I can provide then by all means let me know and I'll provide it.
Click to expand...
Click to collapse
If you were already an expert, you could pare down the details in your post to the minimum amount needed. But when seeking help in an area that is new to you, you should provide the maximum amount of information. If in doubt post more, rather than exclude something when troubleshooting.
Nothing impairs someone from providing effective help as much as missing crucial details. The only things you should withhold are personally identifying info e.g. serial numbers.
Someone knowledgeable trying to help you can easily sift through too much info. Not the reverse.
.
fffft said:
If you were already an expert, you could pare down the details in your post to the minimum amount needed. But when seeking help in an area that is new to you, you should provide the maximum amount of information. If in doubt post more, rather than exclude something when troubleshooting.
Nothing impairs someone from providing effective help as much as missing crucial details. The only things you should withhold are personally identifying info e.g. serial numbers.
Someone knowledgeable trying to help you can easily sift through too much info. Not the reverse.
.
Click to expand...
Click to collapse
I wasn't disagreeing - I've not got any other information to provide currently.
Will try searching the forum more to see if I can find anything else in the meantime.
g935f stuck on logo
hi i tried to remove pattern lock of my s7 edge with z3x but phone just stuck on logo now im trying to take it to download mode but can not boot , just i can go to recovery mode , can anyone help me , is this possible i can flash by sd card.
fffft said:
Your search technique needs polishing. If some particular keyword doesn't work in a search, then use a synonym or reword your search query.
And there is crucial information that you didn't provide earlier. The very reason why I wanted the verbatim context. We are't psychic and can't help you effectively if you don't provide a detailed account.
Adding those details is a huge improvement. You selected a feature (check md5) without understanding how it worked. That caused an error. You then asked us what the error meant without telling us that you had done that and not providing any context or details for us to work with.
The error message, in context, tells us that you either tried to check md5 on a file that doesn't have a md5 - therefore a spurious error. Or the file was profoundly corrupt.
.
Click to expand...
Click to collapse
You should be nicer. That was just plain rude.
guau pues buscais el update.img lo meteis y listo
"read only"?
ggiiaann91 said:
Hi folks!
Just bought myself an S5, have successfully rooted the phone, and decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
I'm on android v4.4.2 - I backed up prior to this so I've just restored back to factory settings for the meantime, but I'd like to know why I'm getting those two errors if possible?
Many thanks!
Click to expand...
Click to collapse
Do you mount your SD card into a USB card reader and then use in a USB port on your desktop or laptop?
because if you accidentally made the "E" port into "read only" on one file, or anything on the drive it could have locked the entire drive down, which to me is exactly
what it sounds like,
put the card back into your desktop, right click as if you were ejecting drive. select properties> preferences> share file settings and set to "Everyone"
yes i know its old, but its not a bad thing to bring up to answer for other newbies right on front page.
thanks this helped me a lot
Greggofaster said:
Do you mount your SD card into a USB card reader and then use in a USB port on your desktop or laptop?
because if you accidentally made the "E" port into "read only" on one file, or anything on the drive it could have locked the entire drive down, which to me is exactly
what it sounds like,
put the card back into your desktop, right click as if you were ejecting drive. select properties> preferences> share file settings and set to "Everyone"
yes i know its old, but its not a bad thing to bring up to answer for other newbies right on front page.
Click to expand...
Click to collapse
I realised I couldn't boot from sd card because I was creating the boot card through a card reader from this post so that really helped me thanks
"Hey i'd rather you do the work for me" kinda thang is a bit annoying. People are so silly sometimes.