Database Develop

Revolution Problems

Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"

Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.

My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.

Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App

Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.

Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk

Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.

Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.

[Q] HTC M7 Dev Edition *Factory Rom Lost*

Hey everyone new poster to the forums here . Have a question about loosing the stock ROM for my HTC M7 Dev edition. I made the backup but I think when I formatted I formatted more then I should have because when I pull up TWRP recovery mode to restore a backup nothing is listed in the window. However when I go into the internal storage in windows on my computer with the phone connected and look inside HTC One\Internal storage\TWRP\BACKUPS I found a folder called HT34GW9xxxxx and a sub directory with a date on it and it looks like the date that I did the flash in the first place. That folder also has 13 files in it equaling out to 4.25GB in size. So basically what I'm getting at is how come I can see this folder here but not in recovery and even if I could see it in recovery this seems like it's not large enough to be HTC Sense 5.0 according to this thread and the downloads attached to it.
http://forum.xda-developers.com/showthread.php?t=2248997&highlight=nandroid
Also speaking of that thread considering the original M7 Dev rom is gone can I use that thread to restore my phone even though I am using TWRP and not clockwork. I'm not the greatest at these type of things, I don't want to brick my phone, and I never have enough time invest in this stuff. If I knew this was going to happy I probably wouldn't have done it in the first place lol.
Thank you in advance and sorry if this has already been talked about, I did a search but I must have skipped over it if it was already out there :\.

dont worry if u have htc one 64gb dev edition go to htcdev..com and download ruu file lock the bootloader and run ruu thats all

Follow up
ccpzcp said:
dont worry if u have htc one 64gb dev edition go to htcdev..com and download ruu file lock the bootloader and run ruu thats all
Click to expand...
Click to collapse
Thank you for the help. A follow up question would be is there a place to get someone's previous backup and download it like the link I put up in the previous posts user did. I really don't want to lock the boot loader and I would love to just be able to easily get Cyanogenmod back on the phone easily. Reason being is that right now the Cm camera just isn't up to pay with the Sense camera software and if I go to an event like I am tonight I would like to be able to swap back and fourth.

TWRP and CWM backups aren't compatible with each other. You'd have to flash the relevant recovery to use a corresponding backup.
You still have your backup though. You said as much in your OP. You just need to go into TWRP settings and specify the default location for your backups.
As mentioned above however, you can just flash the official RUU to return to stock

Thanks a ton!
Just wanna say thanks to the both of you for your help. I went with option 2 for now because I want to switch back to CM after the Cardinals MLB game tonight. I never lost the backup and you were right I just had to find the folder. It was weird I didn't see any button to search for a folder kinda odd how TWRP is layer out in that interface. Yet I found the backed up file and took about 10 minutes from start to finish. The device is still unlocked to so I can reflash CM when I'm ready.
A little off topic but does anyone know what the difference between the GSM Cyanogenmod ROMs and the AT&T ROMs are? I have the Dev version but flashed the AT&T version and it ran fine made calls and had no data transfer issues at all.

Ok so I actually started having issues after that last post. What was happening was I kept getting this HTC system update my guess the Camera software update but whatever. So I clicked on the update now and it downloaded like normal then reboot. After it reboot it booted into TWRP recovery well at that point I didn't know what to do so I just went a head and rebooted into System. Well here is where the issue started it said again system update avalible ok great install, same deal it just booted back into TWRP after the download. Back into system I went and again same thing.
At this point I desided to go into TWRP and do a system restore and I thought that worked cause it wasn't notifying me immediately after the launcher loaded to install the update. So I checked for it manually and of course there was one. Tapped on Install it downloaded and asked to reboot so I did...
SAME ISSUE AHHHHGGG! Lol
This will be the end of me haha.
Is there something I'm missing here? Can I not have root access or a a third party boot loader like TWRP or both modifying the system. What am I missing?
Ok thanks again, sorry for the multiple posts I'm just so frustrated at this point.
Sent from my HTC One using xda premium

This my very wild guess. Try flashing stock recovery first and then install the OTA update again. That's just my wild guess I'm not saying it will 100% work.

No luck
shadowboy23 said:
This my very wild guess. Try flashing stock recovery first and then install the OTA update again. That's just my wild guess I'm not saying it will 100% work.
Click to expand...
Click to collapse
Nope no luck

Hopefully this helps..
What I did find was this link here...http://forums.androidcentral.com/htc...ml#post2827047 that's where someone else is having the same issue but on Sprint I'm guessing. So that doesn't really apply to me. However a poster further down the thread gave another link to all these "nandroid?" files. I'm not really sure what a nandroid is haha I'm such a noob at this. Basically what they are saying is that unrooting it then i guess somehow putting this "nandroid" file on it somehow. Anyone have any idea on this. I'm terribly sorry for my noobishness but I'm trying to learn all this and it's really frustrating at first..
Here's the link to the nandroid files. http://forum.xda-developers.com/show....php?t=2207874 funny thing is that I actually found that link on Android Central website so that I could come back here and repost about it again heh. Anyways does that look like something that might fix the issue that I'm having?
Even if this file does help I have no idea what to do with it but that first link seemed to have some video's attached to it although I worry about following them because it's for Sprint and I really don't want to brick my phone. (another reason I am being so careful) You pay over 600 dollars for a device you tend to be super careful with anything you do with it.

Nvidiafanboy said:
Nope no luck
Click to expand...
Click to collapse
Sorry about that.

All fixed!!
Ok so I got it. I ended up finding this http://qbking77.com/development/how-to-unrootunbrick-the-htc-one-to-stock-2/
Worked great fixed everything. Linked to the RUU on HTC Dev website also so its official.:good:
So basically if Anyone need to restore to factory from a mess they have made follow this guide it works perfectly and he does an execelent job of describing how to do it in a video he posted step by step.

Please help. Phone stuck in purgatory [Resolved]

Okay, so being the wise person that I am, I decided that it would be a good idea to get the 4.2.2 sense update a few days/weeks before my carrier (Rogers) pushes it. I'll write it step by step, in case anyone can help me
- I started by making an ADB Backup, rooting the phone, and installing twrp recovery. No issues there
- When the phone started back up, I tried to restore my data, but the adb backup kept getting stuck on "com.Android.contacts" or something similar, so I decided I might as well try getting S-Off so I could change CID and get the 4.2.2 update.
- I used Revone, but it kept failing (error code -1). I posted in that thread about it, but I decided that in the mean time, I would just factory reset my phone.
I stupidly clicked "format" in twrp!
Now, my phone is on twrp with no OS. I tried downloading the rogers rom from HTC Dev, but it was a Zip file, and it won't install. I restarted the phone, and now I can't push anything to it. It says "error: device not found" when I try push the European 1.28 RUU (which I'm not sure if that would even work, because of CID/MID differences since the phone isn't S-Off.
Any help would be greatly appreciated :crying:

Okay, So I finally got the European RUU to push to the phone, only to realize that it's a ".exe" that can't be flashed from twrp. I have no access to a PC

WhatsAUsername said:
Okay, So I finally got the European RUU to push to the phone, only to realize that it's a ".exe" that can't be flashed from twrp. I have no access to a PC
Click to expand...
Click to collapse
Just flash any stable ROM in the meantime so you can at least boot the phone. Download ARHD, push the zip to your phone, and flash that.

I really don't understand all these people changing CIDs to force updates, especially when they go back to s-on afterward. You're locking your phone into a potentially problematic configuration. I helped another guy this morning who did it and then couldn't boot up but couldn't fix anything because he went back to s-on and locked bootloader.
If you want 4.2.2, do it the right way: S-off, flash firmware, flash rom. If you want stock, there are stock roms. All of this can be done on a Mac.

iElvis said:
I really don't understand all these people changing CIDs to force updates, especially when they go back to s-on afterward. You're locking your phone into a potentially problematic configuration. I helped another guy this morning who did it and then couldn't boot up but couldn't fix anything because he went back to s-on and locked bootloader.
If you want 4.2.2, do it the right way: S-off, flash firmware, flash rom. If you want stock, there are stock roms. All of this can be done on a Mac.
Click to expand...
Click to collapse
Well, I flashed CM 10.1, and finally managed to get S-Off. Now my issue is trying to go back to stock HTC Firmware. I can only get the RUU, which obviously doesn't work on Mac. Even If could extract the Zip, I have twrp recovery. How would I go back to a stock recovery that would allow me to get the OTA? I'm really upset about this whole thing. I mean, come on. HTC should've provided a Mac utility that allows users to go back to stock completely. I understand that they give you warnings about doing this kind of stuff, but I should be able to play around with my device and still be able to get it back to a functional factory state. I got iOS 7, and it was incredibly easy to go back. I've upgraded my Blackberry Z10 a 100 times with firmware from all over the world with no issues. I've also never had to deal with this S-crap stuff on my Nexus 4. It's just frustrating for end users.
Anyways, rant aside, would you happen to know how I can go back to a full factory state? I'm on CM 10.1 right now with twrp recovery.

WhatsAUsername said:
Well, I flashed CM 10.1, and finally managed to get S-Off. Now my issue is trying to go back to stock HTC Firmware. I can only get the RUU, which obviously doesn't work on Mac. Even If could extract the Zip, I have twrp recovery. How would I go back to a stock recovery that would allow me to get the OTA? I'm really upset about this whole thing. I mean, come on. HTC should've provided a Mac utility that allows users to go back to stock completely. I understand that they give you warnings about doing this kind of stuff, but I should be able to play around with my device and still be able to get it back to a functional factory state. I got iOS 7, and it was incredibly easy to go back. I've upgraded my Blackberry Z10 a 100 times with firmware from all over the world with no issues. I've also never had to deal with this S-crap stuff on my Nexus 4. It's just frustrating for end users.
Anyways, rant aside, would you happen to know how I can go back to a full factory state? I'm on CM 10.1 right now with twrp recovery.
Click to expand...
Click to collapse
Without a PC to run the RUU, I'm not sure. You can flash stuff, but if you want to be out of the box stock, you need a RUU.

I finally managed to get my phone to work. In case anyone comes across this, I'll write down what I did.
I had too many problems to list. From not being able to access adb on the phone, to the phone's memory being partitioned incorrectly, to the point where even a recovery like twrp couldn't format or access it in order to flash anything ("Unable to mount internal storage").
The solution to all problems (and if you're a Mac user like I am, this is disheartening), is that you'll need to run RUU on a PC. When doing this, you'll likely run into a few error messages.
Error 170: Make sure the device is in fastboot mode before plugging it in (hold power and volume down on boot, and select fastboot with the power button). You can make sure that the computer can see it by going to your device manager in windows, and make sure that it says "My HTC" under "Android Device." If it has a cryptic name with an exclamation mark, or you can't see it by using "fastboot devices" command, you'll continue to get that error.
Error 171: This error kept occuring when the computer could no longer see the phone after the process had already begun. The reasons this happens are many (ie your USB wire or drive might be faulty), but to me, it was because the phone was not going back to the bootloader on its own, and the computer eventually gave up. To solve this, start RUU.exe and WAIT BESIDE IT. You will come across 2 points where it says waiting for bootloader. Have your computer's device manager open, and hold the phone's power button until you see that the "Android Device" or "My HTC" disappears and reappears. RUU should continue when that happens. Again, you will have to do this twice! If you don't, RUU gives up on the phone as it does not go into the bootloader by itself, and will eventually give you an error.
For anyone going through this, just realize that as long as you can get into the bootloader, there's always a way to get it to work. At times, I thought my phone was completely bricked, but no matter what issue you have (including unable to access the phone's internal memory), you can always solve it if you can get into the bootloader. With that said, this process will erase everything on your phone, unfortunately. Everything is done at your own risk, so please don't blame those who are trying to help you. Good luck, and remember to always post your solution online, if you start a topic discussing the issue. I came across many people with the same issue who never came back with their solution!

Edit the title to solved

Not that it has happened to me but I think you could have just sideloaded a custom Rom from twrp and flashed that.

a box of kittens said:
Edit the title to solved
Click to expand...
Click to collapse
I tried, but I'm unable to do it. Due to the low post count, perhaps? :S
godutch said:
Not that it has happened to me but I think you could have just sideloaded a custom Rom from twrp and flashed that.
Click to expand...
Click to collapse
That was one of the first things I tried. It kept coming back with "unable to mount internal storage" or something like that, as I noted earlier. It was really weird, I couldn't format, mount, or do anything to my storage with tarp, and I couldn't get adb to see the phone. A lot of people have the issue with the One X, but I couldn't find a solution anywhere. I think what made the whole thing trickier than it needed to be is the fact that I changed my CID/MID, and in that guide, it is explained that you have to reboot the phone yourself in RUU, but I didn't realize not doing so would result in errors. I kept thinking it was because my device wasn't being seen in adv, so I was trying to get it to boot into any ROM for that to happen, and the inability to flash anything due to the internal storage error really complicated things. It's good to know that even this can be resolved, as I had all but convinced myself that I was dealing with a brick. I hope anyone coming across this issue in the future can benefit from my ordeal.

WhatsAUsername said:
I tried, but I'm unable to do it. Due to the low post count, perhaps? :S
Click to expand...
Click to collapse
Click edit on the OP, then Go Advanced. You should be able to edit the title at the top.

iElvis said:
Click edit on the OP, then Go Advanced. You should be able to edit the title at the top.
Click to expand...
Click to collapse
Done. Thanks!

WhatsAUsername said:
That was one of the first things I tried. It kept coming back with "unable to mount internal storage" or something like that
Click to expand...
Click to collapse
That's normal since android 4.1 because the sd card is not a fat partition anymore, did you follow this guide?: http://forum.xda-developers.com/showthread.php?t=2325853

[Q] Stuck in Bootloop after fixing permissions in TWRP

Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!

rev89 said:
Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!
Click to expand...
Click to collapse
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).

simms22 said:
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).
Click to expand...
Click to collapse
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.

rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.

simms22 said:
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.
Click to expand...
Click to collapse
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha

rev89 said:
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha
Click to expand...
Click to collapse
you didnt happen to make a backup in recovery, did you? if you did, just restore it.

simms22 said:
you didnt happen to make a backup in recovery, did you? if you did, just restore it.
Click to expand...
Click to collapse
Nope, would have made life a lot easier if I did. I was just kicking myself in the ass for that earlier.

Edit: nvm, forgot you don't have adb access
Sent from my Nexus 6 using XDA Free mobile app

Thanks for the help guys. I'm just gonna start from scratch when I get home... god I hate not having a phone.

Yah I realized fixing permissions messes it up. And also if u wipe internal storage the phone looses the system ui and the back home menu buttons as well

well thats good to know. Will it still do that if I'm not encrypted?

rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.

I can personally confirm the permission fix in TWRP recovery breaks the stock L5.0.0 and 5.0.1 and I assume probably most ROMs? There seems to be several threads about this.

githyanki said:
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.
Click to expand...
Click to collapse
you can flash from a jump drive? I didn't know that

How to Restore Internal SD DATA without DATA LOSS & FACTORY RESET ?

EDIT
You just have to know, that there are some ways to restore everything
In my Case I had Bootloader unlocked already (ofcourse)
And I just was stuck on the TWRP Part... I never knew that was soo easy, but you just have to do it properly.
I will make an extra Tutorial now, because it will save many people from going insane
Because of this I didn't sleep for 40 Hours now already, because I was deeply shocked and some very very nice Pictures and important Communications would be gone... and much work in Optimization etc. etc.
Yes!
Link will follow here!
Here you go for the Solution!
https://forum.xda-developers.com/galaxy-s10/how-to/proper-to-root-s10-device-twrp-s10-10e-t4015813
_________
Hi,
I just tryed to update from beyond rom 5.2 to 5.8 and so I flashed it...
Then I got a Bootloop, because I didn't updated TWRP before.. so I got into my TWRP and flashed TWRP...
But after that I could not got into TWRP anymore, maybe because I forgot to add multidisabler..
So I flashed stock rom...
However Iam now stuck... I have important Data on the Internal SD and also the backup,
But I only come to the points where it asks me to delete all my data.
Is there any way possible to get the data?
Install TWRP somehow or get to a system?
Please suggest whats possible?
It's an emergency...
Hope you can help me & all who have this problem one day.
Best regards

I can only get to standart recovery, normal firmware & system doesn't boot - Bootloop...
I tryd to flash older firmware (ASH1, ASG8 & newer ASK1), but it doesn't boot system, always ask to factory reset and so on....
really ****ed up...

I hope there is another Way, then directly extract the data from the memory component... wich would be very expensive...
https://www.youtube.com/watch?v=nXDUhhyY2rE

basically the new flashed standart rom erases itself after first start, probably because it detects, that the system was modified before (beyond rom) then it reboots itself and there is no system anymore to boot, then it goes in a kind of pre recovery with the option to reboot, factory reset (including all data!) or reading a log...
DAMN I SHOULD BACKUP EVERYTHING ON PC... ALWAYS!
Still I really want to find a solution and I hope some pro can help on the S10.

No Solution for this.... it seems.

Omg i found the solution and got everything back
yes!!!! Great stuff

||||| said:
Omg i found the solution and got everything back
yes!!!! Great stuff
Click to expand...
Click to collapse
Happy to hear you solved... But after reading your other thread and after all of this excitement i still don't get how you solved the problem.... can you specify it?