I have read many times over now jcase method and have tried it twice now without success- clearly I am doing something wrong. I have working adb on my pc and all the prerequisite files in the correct directory. I seem to be going wrong at the "adb restore backup.ab" point- it says allow it to restore but in my terminal that process is very quick and the phone does nothing. Am I not waiting long enough?...and appears as if nothing else happens so I go to first terminal and stop it as directions say...but after that the next important 5 code steps say failed or file not found-is that what is supposed to happen?...I finish the remaining steps and then head to htc un unlock but it comes back FAILED Anyone with success have any tips?? I'm stumped...but not bricked...yet!
are you connected to the internet during that time ?
Allowing it to restore means to acknowledge it on the phone itself. Touch the appropriate button on the phone.
Sent from my HTC6435LVW using xda premium
Unlock your phone and click the allow button.
Sent from my GT-P7510 using xda app-developers app
And after touching the "allow" button,, be prepared to wait several minutes. That command is restoring a 300 mob for. It takes awhile.
Sent from my Nexus 7 using Tapatalk 2
more Q's
Appreciate the help guys! So I should see a message on my phone that requires me to allow? That I did not see or do...sounds hopefull. I have been thinking my adb version was not supporting restore as when I did the restore step all I see is like a help screen, with no direction to allow, or continue or yes/no.....and yes I was connected to internet...should I not be? Won't be able to try this again till tonight but really appreciate the help!
After using the adb restore command, you should turn your phone screen on, and there should be a message waiting that is asking you to confirm that you want to restore.
If you aren't seeing that message after turning your phone screen on, then it sounds like your adb might be too old, our you got a bad download of backup.ab
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Appreciate the help guys! So I should see a message on my phone that requires me to allow? That I did not see or do...sounds hopefull. I have been thinking my adb version was not supporting restore as when I did the restore step all I see is like a help screen, with no direction to allow, or continue or yes/no.....and yes I was connected to internet...should I not be? Won't be able to try this again till tonight but really appreciate the help!
Click to expand...
Click to collapse
I made this mistake last night
is the backup.ab file in the same folder as the adb command is?
I forgot to move the backup file and that is when you get the help screen..
munchy_cool said:
I made this mistake last night
is the backup.ab file in the same folder as the adb command is?
I forgot to move the backup file and that is when you get the help screen..
Click to expand...
Click to collapse
Will check all this stuff out, all sounds like it's pointing me in the right direction and I am a bit complsive so I will get there sooner or later, any other thoughts will be greatly appreciated and investigated...I think my files are where they are supposed to be BUT I will check and re-check
try it and let us know dude ..do not proceed until you are sure backup is done
Ok...some success, did it in win 8 but I think it was my version of adb that was the problem..not version of windows or files-however I had a zillion files and shortcuts on 7 and I was getting confused so I switched.
I did now get the backup to run, unlocked and allowed on phone...let it finish and all seemed great but last step before reboot...the "adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5" code returned something like permission denied? Anyway I did reboot and did try for the hell of it, to unlock at HTC...but of course It FAILED. I did not factory reset this time so I am thinking maybe that's the problem and will try again later. Any other thoughts on this demise?
Maybe windows 8 is the problem
droid DNA \m/ √[π]¶~™
munchy_cool said:
Maybe windows 8 is the problem
droid DNA \m/ √[π]¶~™
Click to expand...
Click to collapse
Could be except that it did work up to that (almost) last step...I did read to factory reboot before trying again but I did not...mostly because I was lazy...but also because the image files were already in my phone storage anyway and that,s what the first few steps do...I started from backup.ab code part so I will do the whole deal over...later-burned at the moment.
Done Deal
rootntootn said:
Could be except that it did work up to that (almost) last step...I did read to factory reboot before trying again but I did not...mostly because I was lazy...but also because the image files were already in my phone storage anyway and that,s what the first few steps do...I started from backup.ab code part so I will do the whole deal over...later-burned at the moment.
Click to expand...
Click to collapse
Well...It all finally went well!! Can't thank members enough for all the help...I will pay it forward!!
Related
This is kind of a rant so bear with me. Got me phone a few days ago, tried to root but found out it was hardware locked from factory. Took it back, they exchanged it, got home and tried to root again... and still hardware lock. So some nice people on here suggested a different method that doesnt involve being able to manually boot the phone into recovery. So I worked up the nerve and downloaded all the drivers, the root file, windows net4, blah, blah blah. I go to open the root file and it wont open. When I right click on it and try to open it the save or run window just keeps popping up no matter what I do. Now IM at a loss, guess Ill just wait for Samsung to release the patch for the hardware lock. Sorry for the long post, Im just frustrated!!
Put your phone into USB-debugging mode, but DONT mount the phone. Then plug it into the computer, install the drivers, and run this program.
http://forum.xda-developers.com/showthread.php?t=739300
Whart do you mean by moubting the phone? Thats the method Ive been trying to use, but I cant get the files open.
I tried rooting my friends phone yesterday, and for some reason, his phone automatically mounted when connected via USB. If its mounted, ADB cannot push the necessary update.zip file to the phone.
GreggoryD502 said:
This is kind of a rant so bear with me. Got me phone a few days ago, tried to root but found out it was hardware locked from factory. Took it back, they exchanged it, got home and tried to root again... and still hardware lock.
Click to expand...
Click to collapse
Take it back again..tell them that you can access recovery mode. Tell them its important to have this function because if for some reason android screws up and you're not able to access your phone to restore you can always run recovery to restore
Ask for one with an august date on the sticker and test it there.
Its a defect and huge headache for you not being able to access recovery.
I exchanged my unlocked vibrant yesterday for other reason and i had them check before i exchanged.
I explained the whole issue with faulty phone with issues accessing recovery.
He went out back came back with one and tried to accessing recovery and couldn't. they only had one other one with the same September date..didn't even try.
So he called a friend of his at a the mall location and he asked him if he had any with the august date. He only had one and he asked him over the phone to test it and see if he could access recovery, and he was able to....long story short return it they will test before you take new phone home and make sure its from august, not september
Wow. The 2nd phone they gave me was a Sept 1 date!!
So unless I return it, rooting pretty much isnt an option!!??
GreggoryD502 said:
Wow. The 2nd phone they gave me was a Sept 1 date!!
Click to expand...
Click to collapse
yea the one he tried and didn't work was from sept.
the unlocked one i returned and new unlocked were both from august
GreggoryD502 said:
So unless I return it, rooting pretty much isnt an option!!??
Click to expand...
Click to collapse
It is but more of a hassle, also note i edited my 1st post.
Also if they dont have any with an august date see if they can call another local tmobile and ask.
I guess ill just wait for a fix or something. Ive already taken one back.
GreggoryD502 said:
So unless I return it, rooting pretty much isnt an option!!??
Click to expand...
Click to collapse
Wow did you even read the link I posted? I don't see how it can be easier than clicking a button on the computer, but suit yourself. I rooted 2 locked vibrants this way.
richan90 said:
Wow did you even read the link I posted? I don't see how it can be easier than clicking a button on the computer, but suit yourself. I rooted 2 locked vibrants this way.
Click to expand...
Click to collapse
Wow, did you even read my original post?? The root file wont open or let me save it. No matter what I click, (save or run), it wont do either. The save or run window just keeps comimg up.
Did you make sure that you are running the program as administrator?
hukkguai said:
Did you make sure that you are running the program as administrator?
Click to expand...
Click to collapse
Yes Im the admin on my computer.
GreggoryD502 said:
Yes Im the admin on my computer.
Click to expand...
Click to collapse
What OS are you running? I'm currently on Vista as an admin and I (STILL) need to set some programs to run as admin and in xp compatibility mode (because Vista is total crap).
GreggoryD502 said:
Wow, did you even read my original post?? The root file wont open or let me save it. No matter what I click, (save or run), it wont do either. The save or run window just keeps comimg up.
Click to expand...
Click to collapse
When you have your usb plugged in, check the notification bar. It should say usb debugging mode and "click here to mount usb" or something along those lines. This means you are not mounted. If that still doesn't work, try getting the update.zip and manually place it at the root of your sd. Then download clockwork recovery from the marketand use that to reboot into recovery to flash the root file.
Sent from my SGH-T959 using XDA App
Whether you are new or a veteran at rooting, you know that rooting is boring!
It's a lot of typing and even making sure you leave the right spaces.. -__-
Last I remember, I posted Ultimate Noob Rooter. It was a great way for people to root, but it had its flaws.
That's when dbzfanatic decided to intergrate some of my ideas with he's and make rooting even easier!!
Very Easy!
I Presend to you:
ULTRA EASY ROOTER
STEPS
1) Download From FileServe - CLICK ME TO DOWNLOAD
2) Extract the .zip folder anywhere you like
3) Open "mt3gs rooter.exe"
4) Read and click "Root Me!"
BIG thanks go to
dbzfanatic - for all his help, efforts, and making the app.
xologist - me, for having the idea to make rooting easier.
nbetcher - who's rooting method we are using
cyanogen - for the .bat he had in he's website that motivated me to making root easier.
As a note this method does use ADB which is included but may require drivers. I will probably be posting a tutorial on ADB setup as soon as I get a reply from svetius about something (proper posting place mainly).
Go ahead and try it though, some systems work "out-of-the-box".
Post reserved cuz we're cool
Problem
I'm trying to root my wifes Slide and am using your program. I don't think it's working with my Dell. When it gets to the step after turning WiFi back on it says Volume up and other steps but the only thing that happens when I hit Volume Up is turns up the volume.
What did I do wrong? I'm a noob to this device, I own a Vibrant and know nothing about the Slide...
Thanks
Alright, does a cmd window pop up on its own?
Edit: also did it find your device? I noticed a bug in my code (accidentally commented a line) that's supposed to kill the program if the phone isn't detected.
I have the same problem and the CMD prompt does come up on its own but its just an endless loop of instructions, press volume button down etc. But nothing happens on the phone it doesn't even restart
I'm also having an issue with not being able to do anything after the menu comes up and says press volume up to apply update. It only turns up the volume. I love how easy this update is, I'm just hoping I'm not making it harder than it seems lol.
Just to update my post, I tried to use the method again and it will not find my phone... It did before twice and now it won't. Strange huh? A little help here please.
Phone is not found and I get the CMD window but never a reboot. I really wanna root this phone with ease!
Just do it the manual way. The root process is fully described here: http://richard.gluga.com/2010/08/complete-guide-to-rooting-and-hacking.html
Good work on trying to make a tool to automate all this, maybe one day we'll get to a true 1-click root method (but by then the Slide will be obsolete and in a museum, lol).
I come from the Vibrant which takes one .zip file and 10 minutes to root with NO PC... So learning all this tech stuff to root the wifes MT3GS is too much. I know others have succeded in rooting with this Ultra Easy Rooter so I'm hoping I can too.
If you can't root this way then there's another way to do it. The method I am reffering to is the no pc root method located here in the forums. Just follow the instructions and it should be pretty easy if you know what your doing. After all it is all going to be done on the phone, which means (no adb required or no pc required)
Sent from my SGH-T959 using XDA Premium App
Got a link? Wait, we are still talking about the Slide right?
I'm wondering if the person that started this thread is going to comment or help solve the problems going on?
The program works perfectly as long as adb sees your phone and is setup properly. I mentioned you needed adb before, that means you need to be able to run adb from any command prompt and not get a prompt saying "adb is not recognized as an internal or batch command" or whatever. I'm tweaking the code so it should run from the adb file inlcluded, just replace the program. That should solve all the issues except if your phone is not found. If it's not you must install the adb drivers for the mytouch slide (install pda.net,easytether,or the latest htc sync with your phone plugged in,that should give you the drivers. you may need to restart).
Edit: also sorry for the delay, for some reason XDA isn't sending me emails when this thread gets replies, plus I was sleeping.
Edit 2: alright updated program attached. I guess everyone who tested and reported had adb setup like me, sorry guys.
dbzfanatic said:
The program works perfectly as long as adb sees your phone and is setup properly. I mentioned you needed adb before, that means you need to be able to run adb from any command prompt and not get a prompt saying "adb is not recognized as an internal or batch command" or whatever. I'm tweaking the code so it should run from the adb file inlcluded, just replace the program. That should solve all the issues except if your phone is not found. If it's not you must install the adb drivers for the mytouch slide (install pda.net,easytether,or the latest htc sync with your phone plugged in,that should give you the drivers. you may need to restart).
Edit: also sorry for the delay, for some reason XDA isn't sending me emails when this thread gets replies, plus I was sleeping.
Edit 2: alright updated program attached. I guess everyone who tested and reported had adb setup like me, sorry guys.
Click to expand...
Click to collapse
Before I read what you posted now, I kept getting the "adb is not recognized as an internal or batch command" so I stopped doing it for awhile to get unfrustrated lol. The program does see my phone but won't write like its supposed to. I'm gonna try it again (I'm determine lol) I have solved the drivers problem(downloaded the htc sync thing) I'm gonna try it again and report back. Thanks for the response and sorry for waking you! *blush*
Don't worry, I woke up on my own . Hopefully this tweaked version works. If you can get adb shell to work in a command prompt and it still doesn't work would you mind sharing the output of a few commands I'll send you so I can figure out what's up?
dbzfanatic said:
Don't worry, I woke up on my own . Hopefully this tweaked version works. If you can get adb shell to work in a command prompt and it still doesn't work would you mind sharing the output of a few commands I'll send you so I can figure out what's up?
Click to expand...
Click to collapse
Okay this time it went thru the commands fine but it didn't reboot or anything. Still stock here. *sighs* Noob question but how do I send you commands lol.
Just copy the output from the cmd window. Try clicking the button again, for some reason sometimes it takes 2 run-throughs to function, sometimes it only takes one. I swear adb hates me, fix one problem 30 more pop up.
It won't let me pull the stuff from command thing but I noticed 2 things, something with exploid and an incorrect password input. The rest breezed thru.
I have changed the build.prop of my rooted TF201 to play the gameloft games.
After changing the TF201 got stuck in a bootloop. I tried the hard reset but it is still not starting.
I read that it is possible to push the orginal build.prop to the TF201 via APX-Mode but i dont now how to do it.
My computer recognizes the TF201 as a Asus Transformer Prime APX mode or in MTP when i start it regular. Unfortunatly i can not get any access to the Data of my TF201.
Is Asus able to see the root and that i changed the build.prop if i sent it to RMA?
Would be so happy if anybody could help me.
Thank you.
(And i know it was stupid to change the build.prop but didnt expected to brick it http://media.xda-developers.com/images/icons/icon9.gif)
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
stf996 said:
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
clmz88 said:
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
Click to expand...
Click to collapse
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Turge said:
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Click to expand...
Click to collapse
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
clmz88 said:
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
Click to expand...
Click to collapse
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
EDIT: Here you go.
http://forum.xda-developers.com/showthread.php?t=1480428&highlight=bricked
Now don't go doing such stupid things again.
Turge said:
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
Click to expand...
Click to collapse
Ok. Thanks though.
I would be happy about some other ideas
Doktaphex said:
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
Click to expand...
Click to collapse
I already got that thread and asked for his solution.
Im unfortunatly not able to sent him a private message because i am a new member.
clmz88 said:
Ok. Thanks though.
I would be happy about some other ideas
Click to expand...
Click to collapse
EDIT: I'll see what I can do for you, give me some time.
Doktaphex said:
EDIT: I'll see what I can do for you, give me some time.
Click to expand...
Click to collapse
Thank you!!!
clmz88 said:
Thank you!!!
Click to expand...
Click to collapse
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Doktaphex said:
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Click to expand...
Click to collapse
I actually dont know what version is on my Prime. I did the official update two weeks ago. So it is probably V9.4.2.11.
I have a app called "adb made easy" on my pc and this on can not find my device.
Does your device constantly reboot or does it stay at the boot animation?
Doktaphex said:
Does your device constantly reboot or does it stay at the boot animation?
Click to expand...
Click to collapse
It stays constantly in the boot animation.
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
EDIT: unplug and plug back in a couple of times, does windows make it's usual connection noises?
Doktaphex said:
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
Click to expand...
Click to collapse
adb made easy and cmd dont show any adb devices.
the devices manager shows
mobile devices: Asus Android MTB Device (could not be started)
windows is always making the pluggingsound
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Doktaphex said:
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Click to expand...
Click to collapse
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Turge said:
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
I think it is setup for MTP but im not sure about it...
I didnt find a way yet to get access to the prime via usb.
Already tried different drivers, adb, apx but nothing is working.
First off,i would like to apologize for being such an amateur.This is my first post on this forum,so don't get angry on me for breaking some rules (forgive me im new ,idk if i should post this here or somewhere else,don't worry i will be polite ).Anyway as the title says,im having a bit of a problem,or to be more precise a huge one.
So lately i was trying to root my phone,Huawei U8500 which was so buggy,so i decided to root it,install cwm and flash a new ROM.But the problem is i can't get it rooted.I've tried many methods from XDA but none of them worked.Z4 root loads until it displayed acquiring root access,and then the app crashes (closes itself).I've tried Framaroot,but it didn't work either.It said 'try another exploit',but the thing is it displayed me only one.I also tried poot.apk,but it also failed.Telling me '(-) can't get a handle on it:-1 Permission denied'.
(note that all the time my USB Debugging was enabled ! ) All of the apps are at latest version!
So after so many failed attempts with pc-less methods i've decided to try a PC one.The first method i used was Superoneclick,which didn't work.I thought that was because the phones model was not supported.All until a friend of mine told me that he rooted his phone using the same program (he has as well huawei u8500).Every time i try to root with superoneclick it is stuck at the second step(as in screenshot).Then i started googleing and google-ing,until i found a thread with a program called SRSroot,thinking it will safe me from this nightmare that is haunting me for days.But it failed again.The program told me 'ADB Device not found',which made me think about checking the drivers.I've installed the google usb drivers and SDK Manager with all drivers.But still the same happens.So i decided to see if my computer(later many others) recognize my device.After i typed in ADB 'adb devices' it showed me blank.Later i tried to do the same with my other phone and it displayed the device.Another thing i've noticed lately is my computer sees my device as a cd device in windows device manager.It happened with all computers i tried. I've tried it also at my friends(plural,which means more computers).I've tried it on Win7,win XP,and WIN8 and it is still displayed as cd drive.(which is not the case with other phones i've tested!)
I hope someone will read this and help me.I would also like to add, this is not my first time rooting,so i knew what i was doing.
Im so confused,idk what to do,developers pls HELP ME!!!
I will also post screenshots from all the things mentioned above.Hope this helps you figure out the problem
On the adb devices, are you sure it is setup correct, because it needs a set of rules basically. I don't have time right now. But if you search 'adb' in the xda portal (not forum) you will find a windows universal adb installer. That should fix the adb issue. But apart from that I don't know what else you can do.
Sent from my ST18i
tried
Guynan said:
On the adb devices, are you sure it is setup correct, because it needs a set of rules basically. I don't have time right now. But if you search 'adb' in the xda portal (not forum) you will find a windows universal adb installer. That should fix the adb issue. But apart from that I don't know what else you can do.
Sent from my ST18i
Click to expand...
Click to collapse
I did what you said,but the problem is the same.The rest of my phones get recognized as androids,but only this unique Huawei is recongized as CD-Drive,pls anyone help?
Here i took a screenshot after trying to update "cd drive''
Beatit123456 said:
I did what you said,but the problem is the same.The rest of my phones get recognized as androids,but only this unique Huawei is recongized as CD-Drive,pls anyone help?
Here i took a screenshot after trying to update "cd drive''
Click to expand...
Click to collapse
Gosh that is so confusing. Could you reset your phone or do you have data you want to keep? Because you could perform an ADB backup and try a factory reset and hope that all is righted.
I did factory reset,i also did hard reset,but still nothing works
Guynan said:
Gosh that is so confusing. Could you reset your phone or do you have data you want to keep? Because you could perform an ADB backup and try a factory reset and hope that all is righted.
Click to expand...
Click to collapse
Already did it,still the problem persists.Anyone here have any idea?
Beatit123456 said:
Already did it,still the problem persists.Anyone here have any idea?
Click to expand...
Click to collapse
Short of a new phone, I got nothing. Unless you could get into a recovery, try format the system, causing a brick, flash a 2.3 ftf and then a 4.04 after that, clearing data each time.
pls read my question thoroughly
Guynan said:
Short of a new phone, I got nothing. Unless you could get into a recovery, try format the system, causing a brick, flash a 2.3 ftf and then a 4.04 after that, clearing data each time.
Click to expand...
Click to collapse
Since im unable to root my phone,i can't flash a custom ROM.I'm trying to root but no success,pls some1 help????
I have searched for 6 hours last night and again for several this morning on all the forums I could.
My phone has nothing left on it except recover. I have TWRP loaded, don't know how, but nothing in any folders.
I was trying to start from scratch with my phone and just wiped everything so I could reload and start over.
Stupid idea I know!
I can get my PC to recognize the phone. I am using Windows 7 and in cmd prompt I can find the phone but I do not know how to sideload or anything like that. I tried following a couple forums on it but no success.
please help
a huge thanks in advance
Minahan1 said:
I have searched for 6 hours last night and again for several this morning on all the forums I could.
My phone has nothing left on it except recover. I have TWRP loaded, don't know how, but nothing in any folders.
I was trying to start from scratch with my phone and just wiped everything so I could reload and start over.
Stupid idea I know!
I can get my PC to recognize the phone. I am using Windows 7 and in cmd prompt I can find the phone but I do not know how to sideload or anything like that. I tried following a couple forums on it but no success.
please help
a huge thanks in advance
Click to expand...
Click to collapse
I think side load is under the advanced options in TWRP, start t there and follow directions.
There is an option in recovery that will lead to this position
Minahan1 said:
I have searched for 6 hours last night and again for several this morning on all the forums I could.
My phone has nothing left on it except recover. I have TWRP loaded, don't know how, but nothing in any folders.
I was trying to start from scratch with my phone and just wiped everything so I could reload and start over.
Stupid idea I know!
I can get my PC to recognize the phone. I am using Windows 7 and in cmd prompt I can find the phone but I do not know how to sideload or anything like that. I tried following a couple forums on it but no success.
please help
a huge thanks in advance
Click to expand...
Click to collapse
In recovery click advanced then click sideload, it then will wait for you to send the ROM. Open adb and you will then enter: adb sideload C:\path\to\rom.zip
After you do that it will slowly start to send it to the device and begin the flashing process
Alternatively you can use: adb push C:\path\to\rom.zip /sdcard/rom.zip
And then just flash it normally.
I got it to work thank you
.torrented and RLGL
I was being impatient, frustrated and very pissed off for my careless actions.
After paying attention to what I was trying to do I did figure out the path I was writing was wrong.
All is well
If anyone is going to attempt or need this fix pay attention to the details.
thanks again guys
It sound pretty bad situation you are facing. Were u missed out some step when wipe it out?
Sent from my HTC6435LVW using Tapatalk