Hi fellow folio owners,
So I got this used folio 2 days ago and I'm already in trouble.
It was rooted when I got it but it has a memory damage error.
I was advised to update it with the latest Toshiba firmware.
The Rom installed but the error is still there. So now my folio is unrooted with damaged memory and no market access.
Already tried the fix mentioned in d3xters OP of the foliomod Rom. But sad enough without the much wanted result.
Is there another way to fix the memory error?
Please help this freaked out folio noob
from what you described, I think most probably it's hardware issues. I think the best way is to revert to original stock rom (which you have already did) and send it back to Toshiba for inspection...
If you already tried the fix for corrupted partitions, I think you have reached the limit of the issues which are already understood - unless you can work out more detail about what the problem is...
Than i guess I have a huge, expensive brick as i don't no how to get more info on the error.
Sent from my HTC Desire using XDA App
Related
I had Magloader and WP7 in it. As time went by I upgraded to HD7 and never looked back. It's been a while since I have touched XDA and WM6.5.
My assumption is that even with Magloader, you only have to flash your stock ROM and it'll revert back to WM.
Mine won't go on and I suspect that I flashed a Non-Tmobile compatible ROM. Can someone confirm that this is the case? Here's the ROM string: RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.0 7U_2.04.50_22_2_Ship.exe
I understand completely that if I messed it up then it's messed up. I just wanna make sure there might be other solutions or something I am missing out.
-Thanks in advance!
----------------------------------
Is this a final answer? I need to know if it's bricked and nothing else can be done.
Anyone thinks a shop may be able to recover it back? It won't go on at all..
tictac0566 said:
Sometimes, it´s easier than you think.
You´ve got 2 options to get rid of HSPL. One of those options would be simply described in the original thread of HSPL.exe software. If you would have checked this program a little bit, you would have noticed the very fact that you can select what SPL or HSPL you want to install.
Second, you can flash your stock ROM via SD card method, this will replace HSLP and everything else - this does not work using RUU.exe via USB.
Click to expand...
Click to collapse
By the looks of the radio installed (2.04.50_22_2), I would say that you did brick your T-mobile phone. Take a look at the following thread for a possible solution to unbrick your phone:
http://forum.xda-developers.com/showthread.php?t=668347
Hi thanks for the response Lavell. Would MTTY be able to do anything?
The phone doesn't turn on at all, or it seems.
I've never bricked one before so Idk if this is the way it happens.
its gone. dead. it will need JTAGging or a new mainboard.
that thread wont help, the phone wont power on, and that thread requires you can get into bootloader.
that's a really early rom you used, the tmous didnt even exist when that rom shipped.
If you want to get rid of it let me know please!!!
Hey guys, don't mean to hijack the thread but I got the same problem here.
Had WP7 but could not use 2g so I went back to MAGLDR113 and installed the file below:
RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.07U_2.04.50_22_2_Ship
It went all the way to 100% but now the phone is dead. Computer makes a sound when I plug in usb but I have tried changing batteries and all but it doesn't work.
Does anyone know in Dallas or areas around how to do that JTAG thing?
There is no proper documentation on how to go back to stock 6.5 Windows or at least I could not find one
S2K_MoZo said:
There is no proper documentation on how to go back to stock 6.5 Windows or at least I could not find one
Click to expand...
Click to collapse
At its most basic, its the same for ALL hd2's, ,
1 get the correct stock rom for your region&vendor
2 flash it
thats it.
Sadly lots of times this is shortened to
1 get stock rom
2 flash it
and people just assume they can use any stock rom, and since they usually already have HSPL installed, it allows the flash to start, and tmous phones die.
Yeh think the HSPL installer should of had a TMOUS version either blocking known bricking radio & ROMs or just an on screen message warrning & advising on checking before comencing with flash.
At end of the day it is the users fault for not researching or using a TMOUS rom to be 100% safer !
http://dl.htc.com/ruudownload/t-mobileUS/Filedownload.aspx?pid=leo
I want to test albertwertz' theory that the problem where some NT's don't boot off SD can be fixed with an intentional brick of a stock NT. Problem is I can't get mine to stock. The unroot app doesn't work on mine for some reason. I've tried with the NT still rooted and it didn't work.
Therefore i need to find a stock ROM and the only one i found has a MD5 mismatch.
Or, I suppose, a solid process for unrooting would also work if anyone knows how to do that..
thanks for the help, If i figure this out I'll make a how to thead.
Its been two weeks now and Im having a major problem. Im running cm10.1 from epinter and using TWRP. I can not delete or add anything to my phone AT ALL. Its to the extent that I cant flash a new rom that was already on my phone ( becasue I cant add new ones) or wipe the existing rom off. Every time I reboot my phone its as it was since the last day I was able to modify it. Its running the same live wallpaper no matter how many times I change it, the same launcher, theme, etc. Ive just tried fastboot because I just got to a pc where I had the proper files to try to return to stock but no success. The only bright spot is that the phone isnt a brick (thank goodness). Im at my wits end and I need some kind of answers because if I need a pc Im limited to the access I have at the moment.
::Edit::
Ive just tried to flash CWM through fastboot but it has no affect on anything. I think the phone is ruined but its a not a brick because it comes on but I cant change anything to it smfh.
No need for a new thread. At least one (extensive) thread exists already. This seems to be a hardware failure, no known fix exists.
Where's the thread that's already covering situations like this?
Sent from my Galaxy Nexus using Tapatalk 2
http://cleanimport.xda/index.php?threads/1967620/
Did you try searching?
I saw similar threads with the "mind of its own" in the title but it wasn't my problem. I've been in this thread since it opened and I've never read about my issue happening to anyone else. Maybe I'm not searching for the right things but the things I tried to troubleshoot first which took some searching. I don't need anyone to get offensive thinking I'm just rambling and wasting time because I wouldn't have made this thread if that was the case. Now I found a thread where people gave testimonials about their issues but they were particular and my issues isn't the same.
Sent from my Galaxy Nexus using Tapatalk 2
Firstly would I suggest you to install CWM instead of TWRP.
Secondly I would suggest you to wipe all the partitions and the internal memory then make a clean install.
If nothing works, it means it's a hardware issue.
Sent from my MB860 using xda premium
The problem i cant flash a new recovery. I tried adb fastbooting but nothing. Ill chalk it up to it being a brick i can never use it or sell it cuz it still carries my info because it wont let mW delete anything.
From me to you through my GNex
Hello guys. I will try to describe my issue very short:
My S3 got bricked a couple of days ago where i did a "NAND FLASH" (yes i am stupid, and i dont know why i did it)
I managed to get my S3 up and running with different firmware, pit, modem, boot files. Now its running STOCK official firmware from S3 without root, and without clockwork...
The S3 is completely stock now, but my issue is:
1. I tried 4 different computers: WIndows XP, Windows 7, MAC etc. but none of them recognize my phone when i attached it, and yes the drivers are installed and i have tried different cables
2. The phone is very laggy and reboots without reason
Conclusion. I think there is something missing in the system files but i have tried every firmware (CYANOGEN too,) but the phone seems to have changed. I think there is a system android file that is still corrupt somewhere or the NAND has been affected by zombies
Please guys... i hope you can help me. -
Test the memory, search here in q&a for the app. I'd guess you have damaged the nand, which will require a motherboard replacement.
you can root using exynos abuse apk. it can be downloaded by qr code reader or directly from phone .after rooting you can use mobile odin to flash the stock rom . this requires no cable or connection to a pc. but first check the memory as boomboomer suggests. if it is damaged you might be able to replace with warranty. good luck
Memory test said "Test has passed" so i think the results are OK?
Ashraf: As i told before: I am already running stock firmware. The phone reboots by it self some times
Any other solutions?
Try the memory test from the freezing thread, if that passes then flash the stock rom again, make sure the csc in the rom matches your country and you have the right modem and RIL either included in the rom or flashed afterward.
Test fully before you log into Google or restore/install any apps. Remove the sd card during this testing.
hi
i had same problem.solved.see this post
http://forum.xda-developers.com/showthread.php?t=2285736
mostafaz said:
hi
i had same problem.solved.see this post
http://forum.xda-developers.com/showthread.php?t=2285736
Click to expand...
Click to collapse
Hello mostafaz... i dont know how to thank you but you solved my issue! I really really appreciate your help and for the solution!
It could be great if we had a database with the official PIT/PHONE etc. files :laugh:
Once again: Thank you!:good::good:
you are welcome
glad to hear u solved ur issue.
i wanna try many stock rom and have no fear ready for new problems
HI Guys,
i have a HTC one S which after restore the touch didnt work anymore.
I tried with ROMs and other flash but no success, Also ordered a new display and still the same.
Please help what to check.
Thanks
BR
dorianshehu said:
HI Guys,
i have a HTC one S which after restore the touch didnt work anymore.
I tried with ROMs and other flash but no success, Also ordered a new display and still the same.
Please help what to check.
Thanks
BR
Click to expand...
Click to collapse
Was the restore from an older update? If so, this would explain it. HTCs are particular about having the same firmware version needed with the rom update otherwise there will be issues with touch, signal, and a couple other things. I would try and run a full RUU from the PC. This should resolve it, if it is software based.
es0tericcha0s said:
Was the restore from an older update? If so, this would explain it. HTCs are particular about having the same firmware version needed with the rom update otherwise there will be issues with touch, signal, and a couple other things. I would try and run a full RUU from the PC. This should resolve it, if it is software based.
Click to expand...
Click to collapse
Thanks es0tericcha0s,
i did restore from the same firmware just after doing a factory reset. Because of the big file size of the restore the process stopped in the middle ( the phone was hot in fact ) and after reboot no touch working. Even after changed the screen still the same.
I did a full RUU.exe but no success and now after doing a lot of things on it, the phone does not mount /sdcard when in CWM recovery mode.
I dont know what to try any more first to fix the mount of sdcard and then try something else.
Please advice .
Thanks
BR
That's not good. Sounds like when the phone got hot and failed to restore that something might have happened to the motherboard. I seem to remember that some HTCs of that generation had touchscreen issues due to something shorting out, but can't seem to find the thread anymore. Sorry. Might be time to save for an upgrade. At least something that gets LTE...