Hi XDA.
This was a thread I started last night ( http://forum.xda-developers.com/oneplus-one/help/one-chinese-import-flash-to-bacon-issue-t2923211) and where it ends is where I realised my device wasn't unlocked. "yeah I know"
So I downloaded and followed these steps shown on this great tutorial https://www.youtube.com/watch?v=5O2e_R_TbVg
But now my phone appears to have no OS. It wont show up as a USB device to allow me to put a zip across to install.
I have learnt alot this evening and am enjoying the process and this is the last step....
If I haven't bricked my phone!
Any help much appreciated.
That's the video that gets you to use a toolkit, right? My first piece of advice: ditch the toolkit and never use one again. They're more trouble than they're worth and clearly cause problems. Plus doing things manually allows you to actually learn a great deal of crucial stuff that you really need to know. Anyway, please provide some more information on your device, is the bootloader unlocked now? Do you have TWRP recovery installed?
Transmitted via Bacon
Hi and thanks for replying. I followed the guide and unlocked and installed TWRP and can access it easily but when tring to re boot the device it just stays on the +1 logo.
I have subsequently tried unlocking again if that was the problem.
Boot the phone into TWRP, go into the wipe menu and perform a factory reset, then reboot the phone.
Transmitted via Bacon
Ok just tried a factory reset and it failed stating among many things.
E:Unable to mount '/data
E:Unable to mount storage
Also the first line was E:could not mount / data and unable to find cry pto folder.
It might be time to start fresh, you're gonna have to try flashing the fastboot images I think.
Transmitted via Bacon
Ok thanks again for your support.
With this in mind can you please give me a nod in the right direction on how to do this please. I appreciate im a little out of my depth here. Swimmimg in deep android.
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Follow step 8.
Yep, that's the one. Keep in mind though that I haven't yet updated that to suit the latest version (38R), so you can download the latest version from here:
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip
And then modify the last command to suit.
Transmitted via Bacon
Ok I'm going in! Will follow those 8 steps however the phone doesn't show as a USB device any more so will this work?
Really sorry guys but step two is a no-go as the device wont boot to enable me to get into dev options.
jnapier10 said:
Really sorry guys but step two is a no-go as the device wont boot to enable me to get into dev options.
Click to expand...
Click to collapse
All you need to worry about is section 8. They're not steps that need to be followed in sequence, they're separate sections.
Transmitted via Bacon
Ok that's a relief. I have completed step one and it says its unlocked.
Ok so im downloading the OS you suggested but cannot get the phone to come up as a USB device to put the new OS onto the internal memory.
jnapier10 said:
Ok that's a relief. I have completed step one and it says its unlocked.
Ok so im downloading the OS you suggested but cannot get the phone to come up as a USB device to put the new OS onto the internal memory.
Click to expand...
Click to collapse
You don't put it on the phone, you need to put it in your adb/fastboot directory on your PC as per the directions in section 8.
Transmitted via Bacon
Yip my bad. Sorry morning eyes and nerves dont mix.
Right installed fast-boot to my desktop and unzipped all files into fast-boot folder.
Ok lets see what happens
Hmmm
jnapier10 said:
Hmmm
Click to expand...
Click to collapse
If you follow the correct instructions you'll see that it doesn't even mention this command...
ONLY follow the instructions in section 8.
Ok everything was going great but on the final step I received this. Thanks again so much for your help, I really appreciate it. I think its close to being sorted.
Gamm86 said:
If you follow the correct instructions you'll see that it doesn't even mention this command...
ONLY follow the instructions in section 8.
Click to expand...
Click to collapse
Yip im again being a chief idiot. I realised just after I had posted.
jnapier10 said:
Ok everything was going great but on the final step I received this. Thanks again so much for your help, I really appreciate it. I think its close to being sorted.
Click to expand...
Click to collapse
Make sure the zip file is in the fastboot folder aswell and make sure the name of the file you use in the command is identical to the name of the zip file.
After the final step your phone should boot again.
Related
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot
DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.
Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.
zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0
same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp
still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point
still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,
Hello all. So need help getting my bearing straight with my TF300T. Mother's tablet I just have it modded for ease of use and now I am lost since it has been awhile.
Tablet is running CM 10.2 with TWRP 2.5.0.0. I don't know what the bootloader is currently on the device. The device is also not being recognized by my computer. I would like to backup her files and get it on CM 11 M5.
I am guessing I need to first figure out what bootloader i am on correct? How do i go about doing this? Next step is to upgrade to TWRP 2.7.0.0 correct and then system wipe and flash CM11? If somebody could either help me out with directions or point me in the right direction it would be great. Extremely familiar with the Samsung scene and just haven't touched this tablet in god knows how long.
Ok so turned off USB debugging and now can see the tablet on the computer. Now how do i go about finding out about the bootloader and updating it.
Edit found that is is US_epad-10.6.1.27.5-20130902
Now I'm a little lost again. http://forum.xda-developers.com/showthread.php?p=49258989 doesn't have the bootloader I mentioned above. Not sure what the safest way to proceed is.
Aali1011 said:
Now I'm a little lost again. http://forum.xda-developers.com/showthread.php?p=49258989 doesn't have the bootloader I mentioned above. Not sure what the safest way to proceed is.
Click to expand...
Click to collapse
You will need to install TWRP 2.7.0.0 to continue. I wrote a guide here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
cmendonc2 said:
You will need to install TWRP 2.7.0.0 to continue. I wrote a guide here: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
Click to expand...
Click to collapse
WOW dude my bad. Can't believe I skipped over the first line in that thread and didn't proceed forward. MY GS3 is giving me "insufficient storage space" issues so android overload right now.
Now stupid question i am on a unlocked bootloader aren't I since i am running a custom rom and what not?
Aali1011 said:
WOW dude my bad. Can't believe I skipped over the first line in that thread and didn't proceed forward. MY GS3 is giving me "insufficient storage space" issues so android overload right now.
Now stupid question i am on a unlocked bootloader aren't I since i am running a custom rom and what not?
Click to expand...
Click to collapse
Yes, your bootloader is unlocked. You can flash the new TWRP from your old one.
cmendonc2 said:
Yes, your bootloader is unlocked. You can flash the new TWRP from your old one.
Click to expand...
Click to collapse
Hmmm go figure. Wonder how I managed to do that when the Asus app was giving me all sorts of issues Thank you for the clarification though. I was lost for a good while.
Hey guys,
I am pretty new to the rooting stuff on the Nexus.
I read the sticky threat from rootSU (http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527) and followed his description. So I installed ADB and fastboot through the "15 sec. installer" (http://forum.xda-developers.com/showthread.php?t=2588979).
So fast so good, everything went fine. But as I tried to "check" if ADB and fastboot are recognizing my device with the command "adb devices" and "fastboot devices" in cmd, I got some strange output (look at the picture).
How can it be that ADB "sees" my device and fastboot not? What I did wrong there?
(I didn't installed the drivers with the 15 sec tool; when I plugged in my device to the computer, it downloaded the drivers itself)
Any help would be very appreciated!
Follow the next step on my thread and install the naked drivers
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Blackbox421 said:
Okay thank you!
I'll try it tonight and report back.
I also thought of a problem with the drivers, but I thought that I messed up with installing ADB and fastboot somehow, because ADB could recognize my device.
One question again: When I uninstall the Nexus 5 drivers and I reconnect my phone to the pc, it download the driver itself.. How can I stop that to install the naked drivers?
Click to expand...
Click to collapse
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
EddyOS said:
Remember - adb ONLY works when Android is booted up or you're in recovery, fastboot ONLY works when you're in the bootloader
Click to expand...
Click to collapse
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Blackbox421 said:
Damn, thats it! I am so dumb! I don't know how I could forget that.. I read it some hours ago.
After I went into bootloader mode, fastboot recognized my device!
Thanks a lot guys, now I can go to the next step to root my device! =)
Btw.. another question, which is offtopic - does it makes a difference to root KitKat or Lollipop? I guess the guides around here are all made for KitKat and I don't want to mess up. :/ Thx!
Click to expand...
Click to collapse
@rootSU has posted some new guides on rooting Lollipop, so best read his threads in the General section
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Blackbox421 said:
Oh I see..thats annoying. But thank you for your answers! I guess I'll read those threads. =)
Btw.. Can you guys tell me if I understood everything..:
To go back to the official 4.4.4., I don't have to root my device, right? I "only" have to unlock my bootloader and flash the official factory image through fastboot. And afterwards I could root my device using the guides around here on xda.
Click to expand...
Click to collapse
That's correct!
EddyOS said:
That's correct!
Click to expand...
Click to collapse
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Blackbox421 said:
Oh, actually thats all I wanted! =)
On my old Samsung Galaxy Ace you had to root your device first, before you even could install another stock rom, thats why I thought it would be the same for the Nexus 5.
Thanks alot, I'll save my data on my PC now and start with the "downgrading"!
Click to expand...
Click to collapse
It's all very easy with a Nexus device
EddyOS said:
It's all very easy with a Nexus device
Click to expand...
Click to collapse
Yeah I think I got it now. I unlocked my bootloader and flashed the official 4.4.4. factory image from the google developers website. Afterwards I booted into the stock recovery and wiped data/factory reset and reboot. Everything is fine now!
Thank you for your help! Learned a lot of basic understandings.
Jnewell05 said:
To root Lollipop you have to use Chainfire Auto Root. There is extra security in Lollipop that keeps the old root method from KitKat from working.
Click to expand...
Click to collapse
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
rootSU said:
There are multiple methods. Cf auto root is just one of them.
I documented all methods in general. There's a link to my thread from "sticky roll-up in general
Click to expand...
Click to collapse
Huh, I thought the methods from your thread would be only for KitKat
Blackbox421 said:
Huh, I thought the methods from your thread would be only for KitKat
Click to expand...
Click to collapse
I usualy root my Nexus by booting into a custom recovery (TWRP), flash the latest superSU.zip and any mod i want and reboot/done That way i keep my stock recovery.
I have a problem with rooting my Oneplus One. It all goes well until twrp needs to start.
My screen is all black and its not reacting to anything. I have to wait till the battery is empty to turn off.
Also when its in this stage my laptop gives me an error: 'USB Device is Not Recognized'.
I hope you can help me.
Did you check the md5 of the recovery image before flashing it? Please copy/paste the text from the command prompt on a flash attempt.
Transmitted via Bacon
Can you access fastboot mode?
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
hazefetish said:
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
Click to expand...
Click to collapse
That doesn't make sense, what do you mean by bootmode? And you didn't answer either of my questions, I asked those for a reason, if you're not going to provide the information that's needed it's pretty much impossible to help you.
Transmitted via Bacon
You can always turn off your phone by holding the power button for 10 seconds.
Try fastbooting the latest TWRP. => http://techerrata.com/browse/twrp2/bacon
It's possible that you have flashed a corrupted file or even a TWRP for a different device.
Alright
Ive tried it again.
At the moment it should boot into twrp the screen turns black.
It shows up as normal adb device, its still connected but my screen wont show me a picture.
I did it with Oneplus One Toolkit 2.0.
Did everything the steps told me.
You still haven't answered my questions...
Transmitted via Bacon
I didnt check the md5 hash but due to the tool its the right iso.
And i cant copy something out of the command promt because it closes automatically.
When i did it the command promt way i didnt even get a message that something failed.
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
hazefetish said:
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
Click to expand...
Click to collapse
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root. And at no point did you mention doing it yourself, you've only mentioned using a tool.
Transmitted via Bacon
timmaaa said:
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root.
Transmitted via Bacon
Click to expand...
Click to collapse
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
When i did it the command promt way i didnt even get a message that something failed.
Click to expand...
Click to collapse
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
hazefetish said:
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
Click to expand...
Click to collapse
My problem is you came here asking for help, and then it took me asking three times over the course of 19 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
timmaaa said:
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
My problem is you came here asking for help, and then it took me asking three times over the course of 31 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
Click to expand...
Click to collapse
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
hazefetish said:
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
Click to expand...
Click to collapse
We can though, we can find out what went wrong by investigating. I'm trying to help you, but I need this information:
Check the md5, let me know if it matches or not.
Make another manual attempt and copy the text here.
And answer whether you've tried any recovery other than TWRP.
Transmitted via Bacon
timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
Listen to Timmaaa.... His guides & other experts from XDA-OPO forums has helped me understand a lot of things about rooting, flashing & other areas.........
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
skyguy126 said:
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
Click to expand...
Click to collapse
It's a nice idea, very generous, but I don't think it's the right way to go, nobody learns anything when using an automated process.
Transmitted via Bacon
I went to wipe my phone to sell it and in doing so I wiped pretty much everything. I can get it go into fastboot mode and load TWRP but thats about it. Please let me know what I need to do to get this thing back up and running. Thank you in advance.
Flash the 44S fastboot images, I have instructions in my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Do I do each of those steps or do I skip some things to do what I need too. I am very new at this and don't understand how to get the rom on the phone to update. Sorry for my lack of knowledge.
I bought the phone already rooted so I didn't do it. I downloaded liquidsmooth rom on the phone and installed in twrp which was easy. I made a nono when I clicked internal memory Im assuming.
They're sections in my guide, not steps. Section 8 is the section you need to do, you don't need to worry about the other sections.
Transmitted via Bacon
Oh Im getting such a headache from this. How do I get adb.exe and fastboot.exe on my computer? Way out of my league here. I may just need to find someone local to do this.
ezekielguy86 said:
Oh Im getting such a headache from this. How do I get adb.exe and fastboot.exe on my computer? Way out of my league here. I may just need to find someone local to do this.
Click to expand...
Click to collapse
Try the 15 second adb installer. Assuming you have Windows.
http://forum.xda-developers.com/showthread.php?t=2588979
Thank you very much. This worked and made me feel like a super computer geek lol. Looks like I lost root but really don't care at this point. Thank you once again.
ezekielguy86 said:
Thank you very much. This worked and made me feel like a super computer geek lol. Looks like I lost root but really don't care at this point. Thank you once again.
Click to expand...
Click to collapse
You can get root again, just by installing TWRP recovery and flashing SuperSU. Again, details are in my guide thread.
Transmitted via Bacon