Related
CWM Backup and Restore: It backs up fine. But it won't restore. I can't remember the error message...something about rfs and can't mount. I know that's not much help. I was wondering if anyone besides me has had problems restoring with this version of CWM, and has a fix for this problem. I have presently done several backups of my stock rooted GB 2.3.6. And I can't restore any of them. As a noob to the Samsung Charge, I have very little knowledge to work with on this. But it seems to me that I read something somewhere that said I needed to use ADB to do something. Darned if I can remember where I saw it. Any help here would be appreciated. Thanks in advance.
The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.
I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.
Perhaps you can IM imnuts to send you a copy of the 0817 version.
trparky said:
The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.
I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.
Perhaps you can IM imnuts to send you a copy of the 0817 version.
Click to expand...
Click to collapse
if you don't mind my asking why is it banned from being posted now? that's the orange 4.0.1.4 version that was up publicly for months and had few issues besides the voodoo menu being removed/disabled... I guess if imnuts ok's it I'll post or pm a link to anyone who needs it
He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.
trparky said:
He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.
Click to expand...
Click to collapse
ah yes I remember, something about imnuts himself wanted to host it to keep track of support and downloads.. nevermind then I won't post publicly but if anyone wants it just pm me
blazing through on my Acer A500 via XDA app
I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?
Lexus One said:
I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?
Click to expand...
Click to collapse
backups may or may not work with the new 5.x CWM, some people say they can do it and doesn't work for others so I'd just stick with the 4.x CWM... voodoo options were removed from CWM due to them not working right or not working at all sometimes when trying to disable lagfix which caused bootloops and softbricks
Same problem on Samsung Epic 4G. Backed up rooted stock FC09 & flashed to CM9 Beta 3. Attempted to restore the stock FC09 & error message popped up. I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.
---------- Post added at 07:52 PM ---------- Previous post was at 07:14 PM ----------
Just Reposting To Give Further Detailed Info
I'm sure you already know of this issue but, I'll re-post here as from my understanding, this is updated most often & I'm really amped about this project.
Major stock Samsung Epic 4G Gingerbread FC09 restore issue.
I did this exactly:
1) Started stock FC09
2) Odin to cwm-5.0.2.7-epic4g.tar.md5
3) Flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip using CWM 5.0.2.7 recovery mode (volume down, camera button & power button combo)
4) Backed up rooted stock
5) Attempted to restore the stock FC09 to make sure it works before I got too into the new release
6) Error message popped up
7) I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.
Again, my deepest apologies but, right now, I'm like the kid who missed the ice-cream truck. I'm not new to flashing but, am new to trying to run a restore. I only wanted the stock FC09 back because Swype wasn't included in the CM9 Beta 3 release & the text messaging background is white (kinda thwarts the sleek, stealthy black color scheme). Will there be a black text messaging background soon? Let me know if I can install Swype using Titanium Backup or any app backup app. If I can at least have Skype, I'll be good as my Beta 2 Bluetooth issue has been corrected.
---------- Post added at 08:03 PM ---------- Previous post was at 07:52 PM ----------
Sorry. I meant to say I flashed Deodexed-FC09-BML.zip before I flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip
---------- Post added at 08:23 PM ---------- Previous post was at 08:03 PM ----------
Brain farts today >.< I also ran a CM9 Beta 3 backup before I attempted the stock FC09 restore. After the FC09 restore failed, I tried the CM9 Beta 3 restore & that worked perfectly so, again, my suspicions lye in the wrong date stamp factor. At some point tonight, I'll test this theory and post the results. If anyone beats me to the punch, awesomeness.
So you bumped a 5 month old thread in the Charge forum to say you had a similar issue with an Epic 4G?
Well
Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.
Casey Stellar said:
Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.
Click to expand...
Click to collapse
You can clearly see at the top of the screen what forum your in. CWM is individually built for each phone, and not every phone is going to support the same features in the same way. Chances are, no one here is going to know anything about the Epic unless someone here just happens to own one.
Wow
Man that thing's tiny. But, as I stated, I didn't notice that & I only posted because the rules say try not to start a new thread concerning a topic that's already been posted. I'm aware each CWM is custom to every phone. I posted the exact details in case someone does notice this thread & has a solution or a definite no it can't be done. I have read on other posts that CWM will restore other custom non-stock ROMs just fine. One source claims people have been able to restore stock back-ups just fine while others have not. But, there were no definite solutions or enough details to go on. Still waiting for a return on that.
XDA (and others) are built around the idea of device specific forums as there are many differences between devices, even in the same family, that prevent anything for one device from working on another. The Droid Charge, as an example, is in the Galaxy S family, but none of the Galaxy S stuff will work directly on it. Even further, the Galaxy S Aviator and the Droid Charge are the same hardware for different carriers, and nothing for the Charge will work on the Aviator. Don't hesitate to make a thread in one device forum just because a thread exists in a different device forum. There's a "Search this forum" button at the top of every subforum. Use it for your device, and post in that forum if you can't find anything.
O.O
Well now I know I've been up to long. I didn't even realize the fact he said "Samsung Charge" nor was I aware there is a Samsung phone called Charge. But, in my defense, I attempted to start a new thread but, as I was typing out a title for the post, the site showed suggestions of other posts that may have my issue already resolved or at least discussed and this one seemed to be the closest. Had I known the Charge was a phone, it may have stuck out more & I would've known I was in the wrong place -_- Silly me. I am glad to announce however that after a little tinkering, I think I have found the solution to my issue. I'll post any results and details in the proper forum. Sorry for any inconveniences.
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped
I've tryed everything to try and root my Samsung Galaxy Tablet 10.1 4G(Verizon) SCH-I905. I've used Bin4ry, tryed to flash cwm via odin(says it successfully flashes, then i try to flash superuser, the recovery still says android.) I've searched and tryed everything to no avail. Can anyone point me to some good directions on how to root this dang device.
Specs:
Samsung Galaxy Tab 10.1 16GB
SCH-I905
Current Android Version: 4.0.4
Anything else just ask.
Hi,
Please give me a few minutes to see what I can come up with as I don't find that device on XDA.
Back soon with my findings- check Post #4.
I'm pretty sure this is the guide that can help. It even claims to be super easy.
http://forum.xda-developers.com/showthread.php?t=1657758
People report success in the thread. But as hinted above, may want to ask in this thread if its for sure for your model.. Before flashing anything.
Good luck!
Edit: I looked through the thread a bit....apparently its outdated. Also, there's posts claiming there's no root method for 4.0.4 for the i905. Perhaps my colleague above will have better luck.
Pony Express said:
Hi,
Please give me a few minutes to see what I can come up with as I don't find that device on XDA.
Back soon with my findings- check this post.
Click to expand...
Click to collapse
Edit: Here is a post on XDA that will hopefully guide you to success in rooting your SCH I905.
And a bit more info from Google.
Also be cautious as Verizon models have been known to be difficult or even not possible to root.
As always, read carefully before proceeding and remember to make a backup first.
Update: Tryed using this meathod: http://forum.xda-developers.com/showthread.php?t=1837605
Official ClockworkMod 6.0.1.2 Recovery:
When i try t flash it says
"Write data size is too big[8|SOS]! [Data:5685248(B) -> Part: 2560/2560(2kb)]
Tegra_Nand_Write: Error to DownloadPartition_odin![0xffffffff]"
The problem I see here is most the guides and posts about that device are quite old. Links end up dead after so long and the files are hard to find.
Its not part of XDA, so use at own risk , but the link "Google" that Pony Express posted may be your best bet.
Hopefully it works out. ?
Pony Express said:
Edit: Here is a post on XDA that will hopefully guide you to success in rooting your SCH I905.
And a bit more info from Google.
Also be cautious as Verizon models have been known to be difficult or even not possible to root.
As always, read carefully before proceeding and remember to make a backup first.
Click to expand...
Click to collapse
I just keep getting the same crap "Signature verification failed" I still have the "Android system recovery <3e>" I've tryed to get CWM recovery flashed but get the error i posted in the last reply i posted.
I can only find out dated info here on XDA. And dead links.
Did you try the Google link above?
Also i've tryed that google one 5 times to no avail says everything goes smooth but then i try root checker or look for SU, nope lol. I mean i've never rooted a tablet before but many phones like Droid X, Droid X2, Rzr Maxx, Rzr Maxx HD. So i mean i know the gist of what should happen yet nothing.
Well, honestly, I could post a dozen links to other websites here....but I don't know what works and what doesn't out there.
My advice at this point. Google "root sch-i905 2014". Look for things posted from this year. I've seen a lot, but can't read them all, or try them obviously. Lol
Hopefully you find what you need. Seems there's others as frustrated as you with the same device. That's what happens when devices age.
Again, good luck!
lancemdewitt said:
I just keep getting the same crap "Signature verification failed" I still have the "Android system recovery <3e>" I've tryed to get CWM recovery flashed but get the error i posted in the last reply i posted.
Click to expand...
Click to collapse
It has been known to happen that once root has been achieved on a device, a manufacturer or carrier will come back and provide an update that causes the root exploit not to work. I have had that personal experience while helping a friend root a device a few months ago.
In summary - your process appears to be sound - unless however there is a device specific recovery ( the one above is for a galaxy s 3 ) that is released after the last carrier/manufacturer update it is likely not to work.
Well thanks for the help anyways I guess I'm SOL, sucks because I don't even like this POS figured I'd like it more rooted....
Hey! I don't know if this is the right place, but I'll try to explain my problem.
Yesterday I got a notification of an update(think it's 6.0.0 (MRA58N)). Today, when I tried to install it I just got an "Error!" message.
I tried to reboot the phone, but nothing happened. It doesn't turn on. However, I can get it into that fastboot screen or what it's called.
Haven't had any problems before, and Im kind of a beginner on these technical issues regarding phones.
So could someone please explain what I should do(hopefully nothing to complicated).
Thanks!
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
dahawthorne said:
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
Click to expand...
Click to collapse
It was new when I bought it (april 2014). I have only installed updates when getting a notification on the phone. I got a notification to do an update yesterday. Did it today. But while updating it just stopped and said "Error!". Turn the phone off, tried to turn it on but nothing happened.
What's the easiest way to make the phone work again?
Have in mind that Im not experienced at all with these stuff . Never had had any problems before
Thanks
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
(Oh, and at worst you can probably flash a new ROM. Don't get too worried just yet... )
dahawthorne said:
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
Click to expand...
Click to collapse
Yes, I updated to marshmallow a couple of weeks ago.
Yes, I was on about 75% battery when trying to update.
As far as I recall it was just the android guy and a red text saying Error! (well it said Fel! because it's in swedish.)
It started to install the updates, but just stopped halfway(rough estimate).
Hmm :/
EDIT: Yes, I've asked on other forums, and they have been saying to flash(it's called taht right?) But since I'm new to this stuff, I want to check all possible alternatives first. And if I decide to do this, I'll have to feel fully prepared on what to do, don't want to screw up things even more
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
dahawthorne said:
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
Click to expand...
Click to collapse
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
I don't know - I suppose it's worth trying. But if the phone doesn't turn on, you'll have to go through the PC setup anyway so that you can work on the phone. Besides, it will come in very useful when you need to do any maintenance on the phone in future (if that's what you want).
Or is there a factory reset in stock recovery? I don't use it myself, so I don't know.
CoJonees said:
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
Click to expand...
Click to collapse
Wug's toolkit needs a fix. It will not load the new Mashmellow either
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Both these threads are unavailable, possibly deleted.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
@beekay
"Want to learn something instead of using a toolkit to do stuff for you?"
You convinced me, but I think that the NRT has a lot of great help in setting up a PC so that you can actually start learning about ADB/Fastboot manual commands.
Although I'd done some minor fastboot stuff before, I'd never done the full Monty and installed a ROM, but I found the experience strangely pleasurable...
@op found help yet :what::what::what::what: