Hello, today I decided to unlock, root my phone. I also decided to install new rom. And everything went fine but befor installing I insted Factory reset I formated data. I don't know what I was thinking. It may be that I was using TWRP Touch for a first time. Can somebody help me get back to at least to Stock if it is possible. Is it possible to connect phone in TWRP to transfer data from computer to it?
BombasMirko said:
Hello, today I decided to unlock, root my phone. I also decided to install new rom. And everything went fine but befor installing I insted Factory reset I formated data. I don't know what I was thinking. It may be that I was using TWRP Touch for a first time. Can somebody help me get back to at least to Stock if it is possible. Is it possible to connect phone in TWRP to transfer data from computer to it?
Click to expand...
Click to collapse
Does mount usb work on twrp? If so you can copy a rom zip to your device. If not than use search here on xda or google you probably need to unroot again and restore with a factory image.
ttl1982 said:
Does mount usb work on twrp? If so you can copy a rom zip to your device. If not than use search here on xda or google you probably need to unroot again and restore with a factory image.
Click to expand...
Click to collapse
Moutning doesn't work.
I found this: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Will this work for me? I was never in this situation before.
You can either use adb to push a ROM zip to your phone, or just flash the stock images to your phone. http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5
Follow this tutorial right here. It'll completely fix EVERYTHING that you are describing.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need the Android SDK for that tutorial, also. Also a brain.
What OS is your PC on?
pyrogoggles said:
Follow this tutorial right here. It'll completely fix EVERYTHING that you are describing.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need the Android SDK for that tutorial, also. Also a brain.
What OS is your PC on?
Click to expand...
Click to collapse
Either Xubuntu or Windows 8.1. What is prefered? Xubuntu probably because you don't need drivers.
BombasMirko said:
Either Xubuntu or Windows 8.1. What is prefered? Xubuntu probably because you don't need drivers.
Click to expand...
Click to collapse
You should use Windows 8.1 for this tutorial. It's aimed towards Windows and the command prompt. Followed word by word, that is, for Windows.
Hope this tutorial fixes it!
pyrogoggles said:
You should use Windows 8.1 for this tutorial. It's aimed towards Windows and the command prompt. Followed word by word, that is, for Windows.
Hope this tutorial fixes it!
Click to expand...
Click to collapse
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
BombasMirko said:
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
Click to expand...
Click to collapse
Virtually every member here has gotten themselves into a situation that they weren't sure they would be able to fix. It happens to all of us. It's Android initiation
BombasMirko said:
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
Click to expand...
Click to collapse
Lol its happened to me so many times that I end up doing it now on purpose just to clean the phone 100% before flashing a new ROM.
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Lol its happened to me so many times that I end up doing it now on purpose just to clean the phone 100% before flashing a new ROM.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Lol I thought I was the only one who does this
Sent from my HAMMERHEAD
Aerowinder said:
Virtually every member here has gotten themselves into a situation that they weren't sure they would be able to fix. It happens to all of us. It's Android initiation
Click to expand...
Click to collapse
Yeah and this is actually the best school to learn new things. Now I know that it is not that bad at all
Related
Hi all.
How can I wipe my Nexus 5 so it is a plain Kit Kat 4.4.2 (like the day I received it) and just root it? it's currently in 4.4.2 and rooted, but with a lot of stuf in it too. My main concern is how to wipe once it's rooted, and how to reroot.
For those who like to read, a little more info:
I have a Nexus 5 which received 2 days ago. I come from an iPhone 5S, so... pretty newbie...
I unlocked the bootloader and rooted the device after unboxing, and have been using it since. Problems are:
1. I just found out about CWM and its capabilities, and I intend to use the backups a lot.
2. I kind of ****ed up with a couple of apps I regret installing.
3. After a backup I just did today, it asked to whether or not fix the recovery (or something like that). Selected YES, nothing happened. It then asked to fix the root... said YES and screwed it completely. I had to put SuperSu in the phone as a ZIP and manually install it again to recover my root access. It kind of looks "dirty" now, lol.
Anyways, I'd like to make a whole device backup from CWM with Kit Kat out of the box, no extra apps installed. Just rooted. Then install all my stuff, sync contacts and so on, and make another backup.
That's why I want to erase the device and have it all clean (just rooted).
Thanks!
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
rwed said:
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
Click to expand...
Click to collapse
It can, but I'd recommend you do it per the link.
jd1639 said:
It can, but I'd recommend you do it per the link.
Click to expand...
Click to collapse
Mmm. OK. And why? (Just curious at this point)
rwed said:
Mmm. OK. And why? (Just curious at this point)
Click to expand...
Click to collapse
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Click to expand...
Click to collapse
lol OK. Thanks guys.
I come from iOS after several years. Please bear that in mind.
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
rootSU said:
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh please, I know. I was just hiding my ignorance under the iOS carpet.
Will give a read to both links tomorrow. Will definitely do link1 on friday if I find the time, and will then consider either doing link2 or going the CF-Auto-Root way.
I'll let you know how this all ends.
Again, thanks!
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
rootSU said:
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
rwed said:
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
Click to expand...
Click to collapse
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
rootSU said:
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
jd1639 said:
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Click to expand...
Click to collapse
rwed said:
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
Click to expand...
Click to collapse
No to both your questions.
jd1639 said:
No to both your questions.
Click to expand...
Click to collapse
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
Not for the nexus 5. I think you're looking at cwm.
jd1639 said:
Not for the nexus 5. I think you're looking at cwm.
Click to expand...
Click to collapse
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
rwed said:
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Click to expand...
Click to collapse
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
jd1639 said:
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
Click to expand...
Click to collapse
I'll just install your file, specially if you can't even tell what that thing I linked is. Thank you jd. :good:
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
That's the twrp manager. Different things. One is an app and one is a recovery
Sent from my Nexus 5
hello everyone,
i'm developing a game with unity and sometimes when i compile and inject the game on the phone it crashes and forces me to factory reset the phone through fastboot. i've done it like 3 times already with no problems.
but today it happened again and the phone just wouldnt recover, i've tried the fix that this video (youtube.com/watch?v=laU6NQ0LxR0) shows but it still does not boot.
I am able to enter fastboot and my computer recognizes the mobile phone so that's a great start :victory:
not sure what guide to follow since i'm not sure whether the problem is on the rom or something else.
can someone give me a tip on what fix should I try? cant really afford to lose my phone right now
it has (had) a stock rom 4.4.2 with stock bootloader, tho i tried to install the fix in the video i've said earlier and i'm not sure whether it changed the rom or not.
thanks
pewtel said:
hello everyone,
i'm developing a game with unity and sometimes when i compile and inject the game on the phone it crashes and forces me to factory reset the phone through fastboot. i've done it like 3 times already with no problems.
but today it happened again and the phone just wouldnt recover, i've tried the fix that this video (youtube.com/watch?v=laU6NQ0LxR0) shows but it still does not boot.
I am able to enter fastboot and my computer recognizes the mobile phone so that's a great start :victory:
not sure what guide to follow since i'm not sure whether the problem is on the rom or something else.
can someone give me a tip on what fix should I try? cant really afford to lose my phone right now
it has (had) a stock rom 4.4.2 with stock bootloader, tho i tried to install the fix in the video i've said earlier and i'm not sure whether it changed the rom or not.
thanks
Click to expand...
Click to collapse
What about following this guide?
Landrea said:
What about following this guide?
Click to expand...
Click to collapse
got stuck here :/
dropbox.com/s/d3s378e9pvxs0ab/Screenshot%202014-03-30%2023.17.12.png
pewtel said:
got stuck here :/
dropbox.com/s/d3s378e9pvxs0ab/Screenshot%202014-03-30%2023.17.12.png
Click to expand...
Click to collapse
Have you configured the drivers on your pc? The phone is recognized? It looks like the pc can't dialogate with it
Sent from my Commodore 64 using Videotel
Landrea said:
Have you configured the drivers on your pc? The phone is recognized? It looks like the pc can't dialogate with it
Sent from my Commodore 64 using Videotel
Click to expand...
Click to collapse
the phone is recognized as motorola adb interface, i even re-installed the drivers. now trying a different rom but i'm pretty sure the ROM is not the issue
*edit: yep, still waiting for device even with different ROM
modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
:victory: :victory: :victory:
this worked for me,
posting the link just in case someone encounters the same problem. thanks
pewtel said:
modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
:victory: :victory: :victory:
this worked for me,
posting the link just in case someone encounters the same problem. thanks
Click to expand...
Click to collapse
Thank you for sharing
/Data gets corrupted
Even, I had the same issue. I tried flashing ROMs through recovery but it gave me error that/data/media/0/ can't be mounted. The only way to get out I found was to full format /data and /storage (philz recovery) and then to push ROM. zip to/sdcard through adb and then to flash it through recovery.
Hope it helps someone.:angel:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?
Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.
Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.
I flashed userdata, and it wiped everything as expected.
But I didn't have a ROM installed. So I'm OSless and there is no OS on the internal SD card anymore.
What do I do in this situation?
RaggleFraggles said:
I flashed userdata, and it wiped everything as expected.
But I didn't have a ROM installed. So I'm OSless and there is no OS on the internal SD card anymore.
What do I do in this situation?
Click to expand...
Click to collapse
Flash factory image or adb sideload a rom in TWRP recovery
GtrCraft said:
Flash factory image or adb sideload a rom in TWRP recovery
Click to expand...
Click to collapse
When I try to do that, the toolkit tries to boot to android and wait for ADB.
RaggleFraggles said:
When I try to do that, the toolkit tries to boot to android and wait for ADB.
Click to expand...
Click to collapse
Don't use toolkits! Download the factory image from 4.4.4 connect your phone to your pc when in fastboot. Then click on flash-all.bat from the extracted image file
GtrCraft said:
Don't use toolkits! Download the factory image from 4.4.4 connect your phone to your pc when in fastboot. Then click on flash-all.bat from the extracted image file
Click to expand...
Click to collapse
Okay, I have a Flash all with Android L on my computer here.
I need a tutorial because it says it's not a command.
RaggleFraggles said:
Okay, I have a Flash all with Android L on my computer here.
I need a tutorial because it says it's not a command.
Click to expand...
Click to collapse
That's because you've not got adb/fastboot in your System Path. You'll need to extract the image to your fastboot folder and then run the flash-all.bat file again
RaggleFraggles said:
Okay, I have a Flash all with Android L on my computer here.
I need a tutorial because it says it's not a command.
Click to expand...
Click to collapse
Sigh...if only XDA had something like that stickied in the general section or something...http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527 <- everything you need is in this thread. Please read it before using toolkits.
PsychDrummer said:
Sigh...if only XDA had something like that stickied in the general section or something...http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527 <- everything you need is in this thread. Please read it before using toolkits.
Click to expand...
Click to collapse
Not to mention a few of us have it in our signatures. Lol
Lethargy said:
Not to mention a few of us have it in our signatures. Lol
Click to expand...
Click to collapse
Wish it could be a banner at the forum. Or even a pop up
Sent from my Nexus 5 using Tapatalk
He may have used a toolkit but at least he gave us an informative thread title.
OP: if you had done your modding without toolkits, you'd know that this is a nothing issue, resolvable in minutes.
Wakamatsu said:
He may have used a toolkit but at least he gave us an informative thread title.
OP: if you had done your modding without toolkits, you'd know that this is a nothing issue, resolvable in minutes.
Click to expand...
Click to collapse
Unfortunately, toolkits and "soft-bricks" are the reason for 90% of threads in Q&A, and the occasional few placed in incorrect sections.
Lethargy said:
Unfortunately, toolkits and "soft-bricks" are the reason for 90% of threads in Q&A, and the occasional few placed in incorrect sections.
Click to expand...
Click to collapse
I think he know. He isn't advocating
Sent from my Nexus 5 using Tapatalk
I fixed the problem on my own guys. I fell asleep and forgot to lock the thread. But now I know toolkits are not bout it.
RaggleFraggles said:
I fixed the problem on my own guys. I fell asleep and forgot to lock the thread. But now I know toolkits are not bout it.
Click to expand...
Click to collapse
Always better to learn :silly:
Lethargy said:
Always better to learn :silly:
Click to expand...
Click to collapse
I am having trouble with SMS now. I been trying to text my girl for 2 days now. They say it's an APN problem, but I don't understand what's wrong with my APN or how to update it.
RaggleFraggles said:
I am having trouble with SMS now. I been trying to text my girl for 2 days now. They say it's an APN problem, but I don't understand what's wrong with my APN or how to update it.
Click to expand...
Click to collapse
Is it just to the one number, or no one is receiving your texts?
PsychDrummer said:
Is it just to the one number, or no one is receiving your texts?
Click to expand...
Click to collapse
It's just one number. I think it's her problem though.
Find a girl with a number you can text to. Whatever you do, the phone stays!
Hi there,
I downloaded the toolbox from here (http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987) several times.
First try I got the notice from ESET Security, that the archive is broken.
Second time I got the notice from ESET Security, that there is a dialer in the archive.
No, 3rd try, I got the notice from first try (archive broken) and the size of the archive is different.
No I´m really confused
Is there a MD5 checksum or s.t. like that?
Just want to try to flash back to 33R from my 38R that I dirty flashed a couple of days ago and then do the OTA.
Eset is marking it a problem, disable Eset. Download the toolbox then mark it safe. Or better yet use adb yourself to flash and do what you nees
Hi Ross!
Thx for reply.
Sure that Eset is the problem?
But why is it that the download has different sizes and is broken?
Haven´t got this problem elsewhere...
Don't bother with the toolbox and use fastboot.
Sent from my A0001 using XDA Free mobile app
Step 1. Ditch toolkit.
Step 2. Learn to do things manually.
Step 3. Be proof proud of your achievements.
Step 4. Be able to get yourself out of trouble when problems occur in future. You won't be able to do this if you use a toolkit because it lets you achieve things without actually learning anything.
Transmitted via Bacon
kokocabana said:
Don't bother with the toolbox and use fastboot.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
timmaaa said:
Step 1. Ditch toolkit.
Step 2. Learn to do things manually.
Step 3. Be proof proud of your achievements.
Step 4. Be able to get yourself out of trouble when problems occur in future. You won't be able to do this if you use a toolkit because it lets you achieve things without actually learning anything.
Transmitted via Bacon
Click to expand...
Click to collapse
I've also mentioned this to some people. Forget toolkits; imagine you encounter a really bad problem yourself... you won't be able to fix your phone because you have no simple knowledge of things like "fastboot" or "adb". Some of these things are really simple and there is a lot of step by step guides and videos to do these kind of things, that is how I learned! I hope you do too. Good luck!
Hi folks,
nice to hear, that anybody knows what to do... but no one is answering to my question
Just to say:
I know, how to use fastboot commands and all that stuff. I probably read all the "how to´s" to flash the stock 33r, but non worked for me.
I downloaded and installed the newest SDK tools, the correct USB-Drivers, did all that stuff. Used different USB-ports on my PC... Did factory flashs in front of flashing... everything.
Enabled USB debugging, unlocked the BL...- oh my gosh, I could go on for hours.
But everytime I tried, I was ending with: "Target reported maximum size..." blablabla.
So the only thing that worked for now, was dirty flashing with TRWP.
But it seems, that there is something wrong. So i wanted to give a toolbox an chance:good:
Why don't you ask your question in the toolbox thread?
Transmitted via Bacon
@timmaaa:
Easy to answer: cause I haven´t had enough posts to do so
You need 10posts to be able to answer in there, so I had to ask in here.
But now I can...
BTW:
I tried once again to flash, using fastboot.
Now it worked, even 4 me :laugh:
Problem was my USB port...
Still had the "maximum size..." error, but finaly everything is on stock 33r now.
38r is downloading already and now installing :victory:
eshoxx1982 said:
BTW:
I tried once again to flash, using fastboot.
Now it worked, even 4 me :laugh:
Problem was my USB port...
Still had the "maximum size..." error, but finaly everything is on stock 33r now.
38r is downloading already and now installing :victory:
Click to expand...
Click to collapse
nicely done, and we all had the same answer about the toolkits, because you didn't explain your true problem to us and your knowledge of doing things.
Toolkits make things very easy, but also makes it easy for people to break their phone.
RossMacgill said:
nicely done, and we all had the same answer about the toolkits, because you didn't explain your true problem to us and your knowledge of doing things.
Toolkits make things very easy, but also makes it easy for people to break their phone.
Click to expand...
Click to collapse
Thx Ross
Yeah, I still dunno why this error-message still appears, even now... when finaly it´s still all okay.
But hey, I dunno have to know everything :silly:
It´s nice to get to knwo your phone and whats possible with it... if u just learn some basic things!
There 4 I love android and my 1+1 :highfive:
Yesterday evening, g.e., I tried the Mahdi Rom.
Did some backup first with TWRP (after I was back @Stock on 38r) and then flashed the rom.
Not mine...
So.. wiped the whole piece and recovered the backup from TWRP- and here we are :laugh:
Thats awesome!
Now I´ll try a different kernel, the franco seems to be a good choice?!
But first I have to learn, what this will mean to me... and my phone
For sure, I´ll never be the guy who´s programming stuff like that... but will be happy to use it