You can hack your PS3 with your evo. Please refer to http://forum.xda-developers.com/showthread.php?t=778202 for the files and informations....
Some points of interest.
1) If you run any rom but fresh, your evo will freeze during the white loading screen, its normal, it will still do the hack. (have not verified myself, I run cyanogen and it freezes on white loading screen, still hacked my ps3)
2) You must have Amon Ra 1.8 or higher or the latest Clockwork Recovery or else you cannot flash the hack to your phone. It will give a digest error.
3) You must have firmware 3.41 installed on your PS3, not 3.15 not 3.42. If you have any other firmware, your ps3 just will not show anything on the screen. If the hack is installed correctly, it will take about 10 seconds, no more.
In order to install firmware 3.41 you can download it from PS3 - Hacks - firmware 3.41 and then visit Playstations Website for installation directions. In order to learn how to update your ps3 WITHOUT doing an auto update which WILL MAKE SURE YOU CANNOT INSTALL THE HACK.
4) Whatever device you load the backup manager package on, will be the only device you can do add backups to. IE: if you load backup manager on your evo in USB storage mode, you will only be able to back up to your evo. I suggest, swallowing 100 bucks and getting an external drive, install device manager to that, then do all your backups to the drive. ORRRRRRRR Buy a 2.5 terabyte drive and install it internally to your ps3.
5) Now instead of a nandrestore there is a disable file you can flash. Check out http://wiki.psfreedom.com/wiki/HTC_EVO
--------------------- Instructions for installing PSfreedom hack with your EVO ---------------------------
1) Bakckup your nandroid then Flash the zip to your evo
2) Reboot your evo (most likely will freeze on reboot, its normal)
3) Make sure you have Firmware 3.41 on your PS3, if not, use an SD card, DVD, or Flash Drive to install the proper firmware.
4) Unplug your power cable to the ps3
5) Plug your EVO into the PS3 via USB cable
6) Plug in your ps3 power cable
7) Press the power buttom immediately followed by the eject button on your ps3 (will beep twice)
8) Wait no longer than 60 seconds for your ps3 to boot, if it does not, refer to the above information about firmwares and files.
9) Once the PS3 boots go to the game menu, and look for install packages.
10) Flash the disable zip file or do a nand restore to your evo.
If you have the option to install packages, its official! You are hacked.
kamitsuna said:
5) Once you have installed Backup Manager to your permanent storage solution, you WILL NOT NEED TO USE YOUR EVO to boot your ps3 anymore. You only need this hack in order to install unsigned code. Once the code is installed, its there permanently. (Have not verified myself).
Definitely NOT true, you will need to have the device plugged in every time.
Click to expand...
Click to collapse
kamitsuna said:
You can hack your PS3 with your evo. Please refer to http://forum.xda-developers.com/showthread.php?t=778202 for the files and informations....
Some points of interest.
1) If you run any rom but fresh, your evo will freeze during the white loading screen, its normal, it will still do the hack. (have not verified myself, I run cyanogen and it freezes on white loading screen, still hacked my ps3)
2) You must have Amon Ra 1.8 or higher or the latest Clockwork Recovery or else you cannot flash the hack to your phone. It will give a digest error.
3) You must have firmware 3.41 installed on your PS3, not 3.15 not 3.42. If you have any other firmware, your ps3 just will not show anything on the screen. If the hack is installed correctly, it will take about 10 seconds, no more.
In order to install firmware 3.41 you can download it from PS3 - Hacks - firmware 3.41 and then visit Playstations Website for installation directions. In order to learn how to update your ps3 WITHOUT doing an auto update which WILL MAKE SURE YOU CANNOT INSTALL THE HACK.
4) Whatever device you load the backup manager package on, will be the only device you can do add backups to. IE: if you load backup manager on your evo in USB storage mode, you will only be able to back up to your evo. I suggest, swallowing 100 bucks and getting an external drive, install device manager to that, then do all your backups to the drive. ORRRRRRRR Buy a 2.5 terabyte drive and install it internally to your ps3.
5) Once you have installed Backup Manager to your permanent storage solution, you WILL NOT NEED TO USE YOUR EVO to boot your ps3 anymore. You only need this hack in order to install unsigned code. Once the code is installed, its there permanently. (Have not verified myself).
6) Now instead of a nandrestore there is a disable file you can flash. Check out http://wiki.psfreedom.com/wiki/HTC_EVO
--------------------- Instructions for installing PSfreedom hack with your EVO ---------------------------
1) Bakckup your nandroid then Flash the zip to your evo
2) Reboot your evo (most likely will freeze on reboot, its normal)
3) Make sure you have Firmware 3.41 on your PS3, if not, use an SD card, DVD, or Flash Drive to install the proper firmware.
4) Unplug your power cable to the ps3
5) Plug your EVO into the PS3 via USB cable
6) Plug in your ps3 power cable
7) Press the power buttom immediately followed by the eject button on your ps3 (will beep twice)
8) Wait no longer than 60 seconds for your ps3 to boot, if it does not, refer to the above information about firmwares and files.
9) Once the PS3 boots go to the game menu, and look for install packages.
10) Flash the disable zip file or do a nand restore to your evo.
If you have the option to install packages, its official! You are hacked.
Click to expand...
Click to collapse
i appreciate your help to the community and i have implemented some of it into my thread but some of the info you posted is wrong such as device manager, i believe you mean back up manager and that is not true that you need to install it on there. Anyway, thanks for the help, i have added it to my post, but i dont think this thread belongs here, more like answers part of forum.
#5 sounds wrong. I doubt the PS3 will ever run your unsigned code without the PSFreedom hack enabled by the Evo at every bootup, even if successfully installed on a previous boot.
WIIWONWON said:
kamitsuna said:
5) Once you have installed Backup Manager to your permanent storage solution, you WILL NOT NEED TO USE YOUR EVO to boot your ps3 anymore. You only need this hack in order to install unsigned code. Once the code is installed, its there permanently. (Have not verified myself).
Definitely NOT true, you will need to have the device plugged in every time.
Click to expand...
Click to collapse
beat me to it as i was typing lol, i added a little bit of his post.
Click to expand...
Click to collapse
That is possible, Backup Manager will remain installed i guess but will no longer function.
Post has been edited to reflect this.
It also makes the evo a fairly useless way to hack your ps3. 15 minutes to turn on your ps3...bleh
In any case, thanx for correcting me guys. Im no developer, i just know all the questions i ran into, and they happen to be the same questions people keep asking. Figured id try to keep it simple.
Good info (seems to be copied and pasted from the PSFREEDOM thread).. I'm sure we will see this skip to QnA tho. Question is even in the title
iitreatedii said:
i appreciate your help to the community and i have implemented some of it into my thread but some of the info you posted is wrong such as device manager, i believe you mean back up manager and that is not true that you need to install it on there. Anyway, thanks for the help, i have added it to my post, but i dont think this thread belongs here, more like answers part of forum.
Click to expand...
Click to collapse
Is it necessary to quote the entire first post?
Sent from my badass, superfast evo; over the fastest, cheapest, best coverage-having network.
So i got the ps3 to come up with the "install package files", so i know i'm hacked, but now what do I do? Do I have to hit install packages or what? Thanks in advance
Edit: Also where can I get backup manager?
barnacles10 said:
Good info (seems to be copied and pasted from the PSFREEDOM thread).. I'm sure we will see this skip to QnA tho. Question is even in the title
Click to expand...
Click to collapse
To clarify, the info in the psfreedom thread, is copy and pasted from here, as stated above.
So i got the ps3 to come up with the "install package files", so i know i'm hacked, but now what do I do? Do I have to hit install packages or what? Thanks in advance
Edit: Also where can I get backup manager?
Click to expand...
Click to collapse
You can now install package files. Google for backup manager.
I see no point on using my phone to play games on the PS3... why not to make it work with old phones (the ones that you just use as a paper weight). I have two PS3's at home and believe me I still see no point on using my evo to play games on the ps3 hehe. Don't get me wrong, I like the idea but, what about if somebody calls you and you are playing.
This will be much more streamlined when a psfreedom AMON_RA is released for our phones. Then you can just open Rom manager, click boot into Recovery, and hack the ps3, then reboot and you phone is normal again.
At that time, Bart will be my hero. (even more)
technically you rent using it to play games youa re using yor phone to put your ps3 in dev mode. while in dev mode you can play games (if you install back up mamager) or use homebrew apps with out the aid of your phone once in dev mode.. Personally i still think it is a hassle and i think Sony will crack down on those they can catch. It is kind of a pain to have to flash your phone start your ps3 and either flash or annd restore your phone back each time you want to power on your ps3 and use it in dev mode (which is needed to play the back ups).
just me. I am sure the kiddies that have nothing better to do and no jobs will love this and wont mind though.
gatorran said:
I see no point on using my phone to play games on the PS3... why not to make it work with old phones (the ones that you just use as a paper weight). I have two PS3's at home and believe me I still see no point on using my evo to play games on the ps3 hehe. Don't get me wrong, I like the idea but, what about if somebody calls you and you are playing.
Click to expand...
Click to collapse
You dont have to leave your phone plugged in. Once the ps3 has booted up you can remove it. takes 10 seconds.
Guys this literally takes 5 minutes.
-flash the enabler
-plug phone into ps3
-unplug ps3
-plug in ps3
-power on then hit eject
-unplug phone and restore from nandroid
Piece of cake.
then you wait 10 minutes while your phone finishes restoring. thats also assuming you are ok with the nand back up you have and havent changed anything since you made it if you have you either have to manually make the changes or make a nand back up first. 5 minutes is now 15-25. and that is EVERY time you turn on the ps3. is it cool that you can do it sure, is it hard to do no it isnt, but if you find this as an optimal solution or even a sustainable one then i don't know what to tell you.
omegasun18 said:
then you wait 10 minutes while your phone finishes restoring. thats also assuming you are ok with the nand back up you have and havent changed anything since you made it if you have you either have to manually make the changes or make a nand back up first. 5 minutes is now 15-25. and that is EVERY time you turn on the ps3. is it cool that you can do it sure, is it hard to do no it isnt, but if you find this as an optimal solution or even a sustainable one then i don't know what to tell you.
Click to expand...
Click to collapse
Im playing tiger woods while my phone restores so I dont pay attention to how long it takes. Im sure there will be a much simpler solution in the future but this one works perfectly fine for me.
how do you install psfreed recovery .img??
I know that it says by fastboot, but are there any step by step instruction? thanks for the help
Related
This is the latest release of my fix (June 14, 2011). This version addresses the Market ID and Moto Blur issue.
This version does not require the use of scripts on the phone. It uses ADB and sqlite3 (both are included in the zip file).
I created a new thread here because the older version was so full of bugs and comments about said bugs I figured it was time to start fresh, seeing how I am using a different method (the method I should have used to begin with) for this hack. Also, this should have been in development to begin with.
I have not had a chance to test the latest version, aside from verifying the awk command works as exptected. The rest is a strong educated guess, mixed with a re-tooling of it to just use Android Debug Bridge to do what I was having scripts do in the past. Should be much more reliable.
IF YOU DECIDE TO USE THESE INSTRUCTIONS: PLEASE, read through this page entirely from top to bottom at least once prior to doing anything. This way, if you are unsure on anything, you can ask the questions you need answers to. I am not liable for anybody messing up their phone because they didn't think to read the F'n manual prior to following these steps.
If you don't read this through completely before starting, and you brick your system, Don't come crying to me. I warned you.
This version makes it close to impossible to brick the system, but I left that bit in to cover my arse.
If you do not have the phone rooted, download the second zip file, and install the drivers found below:
Motorola Driver(install before you run the batch file)
You will need to enable USB Debugging:
On your phone,go to Settings->Applications->Development->Check "USB Debugging"
Latest version installs busybox for you, but if it doesn't, the script will pause for you to check, and tell you how to quit out of my script before proceding. If you have issues with that, let me know. I haven't tested this version, but by all accounts, it should be more reliable than my previous iterations, with the plus side of not having to purchase an app.
I have not tested it, so you may still need to tell it to install, but it should install the apk.
1. Download the attachment located in this post.
Unzip to a folder on your desktop.
PLUG IN YOUR PHONE NOW!!!
Double click on the batch file ("enable_unknown_sources.bat"). You may have to run as administrator, but I don't think so. Built on Windows XP (I'm a linux guy who wrote this at work in a couple minutes)
When it prompts for you to OK the super user for "unknown", look at your phone. It should have a prompt. If not, it may be ok. We will see....
once your phone has rebooted, you phone will have "unknown sources" enabled already. Don't worry about rebooting. The batch file did that for you.
Quite a bit less work than before. Good news: it's done! never to worry about it again...unless you upgrade....
DISCLAIMER:
DO NOT FOLLOW ANY OF MY STEPS IF YOU ARE UNSURE OF WHAT YOU ARE DOING! I have done my best to ensure that the instructions are accurate, but I made mistakes in the first revision, so who's to say that I didn't miss something this go 'round as well? If you decide to follow this walk-through, your actions are an agreement to not hold me liable if your phone becomes a pretty brick. I am not responsible for what you do with this information. If you have no idea how to do any portion of these instructions, you can either walk away (best idea), or ask for help here.
I am also not the 2nd shooter on the grassy knoll, nor am I the cause of all your woes throughout life. I always wanted to say that in a disclaimer.
Thanks to Vahnyyz for reminding me that I forgot to have you enable USB Debugging.
IF YOU HAVE PROBLEMS:
Have you installed the Motorola Drivers?
Do you have Debugging enabled?
If the answer to the 2 questions above are "yes, damnit! Give me a good answer, and stop wasting my time with these stupid questions", then you will need to tell me at what point the scripts fail. I will look into the problem as fast as I can.
so I tried the program you put on and everything because I haven't been able to root my phone as of yet, but the file I downloaded that included rooting did not work, everytime I ran the application it stated that "Device Not Found" and my phone is connected through USB at the moment.
Forgot a part
Thanks for letting me know about your issue. You need to do the following:
Ensure you have installed the drivers on you computer
Ensure USB Debugging is turned on
To enable USB Debugging, (on your phone...duh) go to Settings->Applications->Development->Check "USB Debugging"
as soon as I run the. bat file, command screen tells me to make sure that busybox is installed, which it is, to unplug phone, go to, busybox and install. Wife's phone is already rooted, once I hit next, "unknown" will pop up on the screen for a second and then....nothing.
Need to fix that to state "....after you ensure busybox is installed, plug phone back in"
Just plug the phone back up prior to proceding
Sent from my GT-I9000 using XDA App
How is the no blur version coming along....anxiously waiting for that!
JBallin4life27 said:
How is the no blur version coming along....anxiously waiting for that!
Click to expand...
Click to collapse
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
jonsjava said:
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
Click to expand...
Click to collapse
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
JBallin4life27 said:
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
Click to expand...
Click to collapse
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
jonsjava said:
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
Click to expand...
Click to collapse
Yea lol...no idea what that all means...sorry i'm not any help
Since no one posted here yet, I will.
THIS IS STRICTLY FOR SPRINT TAB ONLY.
Here is all the step you need to get your tab updated to Gingerbread. Thanks to ZoinksS2k for the guide and pvtjoker42 for the file.
First you have to have stock EB28 on the tab. If not follow these steps:
Download the E24 flasher
Find a copy of Odin (1.3 worked for me)
Extract the flasher, look in \Models\Binary, strip the .MD5 extension from the file SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar.md5
Load Odin
Connect device via USB
Reboot into recovery (power off, hold power and down volume keys or do a "adb reboot download")
Select the newly renamed .TAR file in the PDA slot in Odin
Select start (flashing should commence)
Boot, then you will be prompt for EB28 update, allow the EB28 update to complete
Then follow these step to update to Gingerbread:
Download the Gingerbread update (Special thanks to pvtjoker42 for this. Source)
Copy the update_from_EB28_to_EF17.zip file to the root of your SD card, rename it to update.zip
Reboot into recovery (power off, hold power and up volume keys or do a "adb reboot recovery")
Use volume rocker to select apply update.zip (or whatever)
Touch the home button to select
NOTE: If you got stuck during the update, try to reformat the sd card with your tab or use a different one, then try again
Warning: You will lose root on the tab, and there is not a solution to root Gingerbread yet...
Enjoy!
Downloaded, renamed and flashing using the recovery.
Now I'm at a screen with little android with triangle with ! sign..
is this normal?
Hold in power for like 20 seconds (power off), then power on like usual.
Boot normal? Yeah!
Stuck at samsung logo? Bad flash. Return to step one.
i am also stuck at the screen with the android guy and the triangle
kholy said:
i am also stuck at the screen with the android guy and the triangle
Click to expand...
Click to collapse
Try to format your sd card or use a different card.
siptang said:
Downloaded, renamed and flashing using the recovery.
Now I'm at a screen with little android with triangle with ! sign..
is this normal?
Click to expand...
Click to collapse
I had to reformat the SD card on the tab itself and then try the update.zip in recovery. Don't reformat the card via windows, that didn't work for me.
I posted this in the GB update thread as well.....
Can someone pull a nandroid, and a roto for me of the sprint gb stock after install, pm me and ill give you an ftp account to upload it.
Make sure....for the love of god, please remove your personal data first.
I could use a clean system dump to start on some roms in gb.
oldmacnut said:
I posted this in the GB update thread as well.....
Can someone pull a nandroid, and a roto for me of the sprint gb stock after install, pm me and ill give you an ftp account to upload it.
Make sure....for the love of god, please remove your personal data first.
I could use a clean system dump to start on some roms in gb.
Click to expand...
Click to collapse
Do a Factory reset before you do a nandroid or a roto. That way no personal data will be there before you send it to Oldmacnut
oldmacnut said:
I posted this in the GB update thread as well.....
Can someone pull a nandroid, and a roto for me of the sprint gb stock after install, pm me and ill give you an ftp account to upload it.
Make sure....for the love of god, please remove your personal data first.
I could use a clean system dump to start on some roms in gb.
Click to expand...
Click to collapse
Sorry for the noob question but can you instruct how to do this? Would save me sometimes researching. Thanks
Thanks! I was spamming the update firmware button and getting nothing. i knew someone on XDA would have my back. That's why i love this community!
I dont have root or cwm. Everything installed fine. The only possible issue I see that wasnt happening with ea24 and eb28 is the battery isnt charging when connected to a computer. There is a red X in the battery. Before, this happened when I had cwm 3000 on with eb28. When I flashed back to complete stock and only rooted, it started charging through usb like it used to. Can anyone say if they are experiencing this also? I am thinking something is not right here.
Update
Hey darkpal, its oldmacnut not oldmacunt. Lol
To my knowledge the Tab will NOT charge via computer USB. It has to be plugged in to the stock power adapter. Something about the voltage or amperage (I don't remember which) is too low from a pc USB port. It will run off the USB without draining the battery, but it will not charge.
im assuming someone is working on the root? :]
siptang said:
Downloaded, renamed and flashing using the recovery.
Now I'm at a screen with little android with triangle with ! sign..
is this normal?
Click to expand...
Click to collapse
OMG are you a senior member ? its called the downloading mode !! press the power button to switch off and than fire it up !
gtdnodude said:
To my knowledge the Tab will NOT charge via computer USB. It has to be plugged in to the stock power adapter. Something about the voltage or amperage (I don't remember which) is too low from a pc USB port. It will run off the USB without draining the battery, but it will not charge.
Click to expand...
Click to collapse
It was charging fine via USB in Froyo builds EA24 and EB28, so this must be some kernel issue with EF17. We should report this to Sprint and Samsung (and Google?) as an issue.
coferjinelong said:
im assuming someone is working on the root? :]
Click to expand...
Click to collapse
Google patched the Gingerbreak exploit so we'll most likely only see root once there is a custom kernel. Hopefully we'll see that soon..
pvtjoker42 said:
Google patched the Gingerbreak exploit so we'll most likely only see root once there is a custom kernel. Hopefully we'll see that soon..
Click to expand...
Click to collapse
Speaking of custom kernels, are there any developers working on that? Kernel sources for Sprint Tab were released by Sprint/Samsung last week, but I haven't seen any interest on XDA.
IMO... Tab looks the same as before. Are there any differences than Froyo besides it saying build: Gingerbread & battery not charging with usb? I just changed SD cards and it updated fine.
Edit: Quadrant Advance running @ 1615
I don't know if it's my imagination or not but it seems like the four action buttons on the bottom aren't registering a touch as easy as they used to. Reminds me of my old moment. I'm clearly touching dead center of it yet nothing is happening right away. Speed wise, I'm not noticing anything of an improvement.
Guys, need your help!
The following are the steps i tried, and failed:
Step 1. 2GB Micro SD - Lexar
Formatted FAT32 - NO GO
Formatted inside my tab - NO GO
I figured may be the card is bad
Step 2. 2GB Micro SD - Kingston
Formatted FAT32 - NO GO
Formatted Inside my tab - No Go
I figured may be because i am 'rooted', so i wiped the tab clean (Power + Vol UP), Wipe Cache clean
Step 3. 8GB Micro SD - SanDisk
Formatted FAT32 - No GO
Formatted Inside my tab - NO GO
Problem: the update goes about 1/4 and then the triangle with "!" appears
I dont mean to sound like a dufus, but can anyone point me to the right directions?
Thank you
the phone is a sprint gnex.
i had twrp as recovery, and i was playing around with it, got distracted, and my 2 year old grabbed it and wiped everything. no OS, no recovery, no nothing.
i'm not even sure where to start. my newbie self is thinking maybe odin? i used adb once, is that where i should be looking?
i guess my question is where does one start when he has no OS. and i could sure use a link for wherever factory images, or tar files, or whatever, are reposed.
please help a brother out, and keep in mind i am in fact over my head. just trying to salvage this if possible. it is not an urgent thing, as i the device is merely used as a media device for my 2 year old.
my laptop is a windows 7 device. i've downloaded usb drivers for samsung, odin, and adb fastboot. they are sitting in my download folder as zip files. that is where i stand.
boathead said:
the phone is a sprint gnex.
i had twrp as recovery, and i was playing around with it, got distracted, and my 2 year old grabbed it and wiped everything. no OS, no recovery, no nothing.
i'm not even sure where to start. my newbie self is thinking maybe odin? i used adb once, is that where i should be looking?
i guess my question is where does one start when he has no OS. and i could sure use a link for wherever factory images, or tar files, or whatever, are reposed.
please help a brother out, and keep in mind i am in fact over my head. just trying to salvage this if possible. it is not an urgent thing, as i the device is merely used as a media device for my 2 year old.
my laptop is a windows 7 device. i've downloaded usb drivers for samsung, odin, and adb fastboot. they are sitting in my download folder as zip files. that is where i stand.
Click to expand...
Click to collapse
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
ashclepdia said:
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
Click to expand...
Click to collapse
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
boathead said:
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
Click to expand...
Click to collapse
Why can't you get into recovery?
Are you choosing recovery mode via the bootloader menu? I didn't think it was POSSIBLE to wipe recovery from within recovery.
Even if you can't, trust me, Doing a factory img restore, or using fastboot to flash custom recovery again is VERY easy. To get the SDK that has needed fastboot tools, go here http://developer.android.com/sdk/index.html#ExistingIDE
And grab the needed exe for your setup(windows 64 or 32bit). Make sure you are getting the "ADT bundle" it's what has needed platform tools. Then just run the exe and follow instructions.
Now u COULD also just Google search for Wugfresg toolkit, and download and use that. Its very easy to use as well. I just prefer to have adb and fastboot installed to my computer so that I can always be good to go. Plus I use Linux so Im not able to use Wugfresh, but knowing how to just use fastboot and adb also makes ya feel like a boss(even though is pretty simple lol)
Don't worry, there is hope, and it's not gonna be difficult. You'll be up again in no time.
because you said you didn't think it was possible to wipe recovery from recovery, i went into bootloader. you are correct. in my panic i overlooked it. i DO in fact still have twrp.
but there is nothing to restore or install. so once my phone charges, i'll give it a shot as you suggested. would you kindly check in later in case i need some more help?
thanks my friend for steering me in the correct direction.
boathead said:
because you said you didn't think it was possible to wipe recovery from recovery, i went into bootloader. you are correct. in my panic i overlooked it. i DO in fact still have twrp.
but there is nothing to restore or install. so once my phone charges, i'll give it a shot as you suggested. would you kindly check in later in case i need some more help?
thanks my friend for steering me in the correct direction.
Click to expand...
Click to collapse
Of course!
I'm always checking in these forums, and I use Tapatalk, and have actually grown fond of Tapatalk notifications, so I SHOULD get a notif if you post back or PM(though I prefer to keep in thread, that way someone else searching for answer to similar issue can find a helpful thread as well)
Yea it sounds like your little one got into twrp and most likely wiped all of /data and /system. Instead of just a regular factory reset which would have left your stuff like flashable zips and all still in /sdcard. That sucks! I've actually done that on accideHahaha
hile back(a mistake you only make once to wipe all of /data AND /system lol, even though can pretty easily be fixed)
Sounds like you could use adb sideload or push to get ROM/gapps zips back on the device, or just go with a total device factory restore, whichever you choose at this point should work just fine.
I'm not sure if there is a way to do this yet, but I've always wanted to put a pin code lock for TWRP. That way if my nephew ever did find his way into there when using my phone, he wouldn't be able to do any damage. If it's not a part of custom recovery yet (I haven't looked actually lol) it would be awesome if someone found a way to add that feature in. Could save a lot of us the hassle in cases like this! Hahaha
I'll check back in the morning and randomly tomorrow (some of the day I won't have a connection, I use Gnex strictly on WiFi) to see if you need any help/tips/clarifying of any steps needed. Once you do this restore process once, you'll be amazed at how easy it can be, and as long as you keep the files on your laptop, you'll be ready to go if you ever need to do it again.
success!
i had a great deal of trouble sorting the drivers....took quite a while to get the pc to recognize the device. then i got confused about a few things...stunner, i know, but was able to reflash a factory image with the wug toolkit. so i guess i took the cowardly way and didn't do the adb route.
anyway, i'm good to go. i am left with the initial problem that had me in recovery in the first place. i figured flashing a rom would solve it, but no. so i'm left thinking it is on the server side. at least i have something to work with now.
so thanks again. without your calming words i never would have gotten this going. i don't have the temperament to play around with my devices, i've learned.
boathead said:
success!
i had a great deal of trouble sorting the drivers....took quite a while to get the pc to recognize the device. then i got confused about a few things...stunner, i know, but was able to reflash a factory image with the wug toolkit. so i guess i took the cowardly way and didn't do the adb route.
anyway, i'm good to go. i am left with the initial problem that had me in recovery in the first place. i figured flashing a rom would solve it, but no. so i'm left thinking it is on the server side. at least i have something to work with now.
so thanks again. without your calming words i never would have gotten this going. i don't have the temperament to play around with my devices, i've learned.
Click to expand...
Click to collapse
That temperament is something that is gained. MOST of us have been in that "oh holy crap what do I do now?!?! Im not prepared for this!!" Moments (my first one was on my birthday back when I had DroidX2, and didn't have my own computer to restore it using RSDlite sbf flash.. I accidentally flashed something that didn't work, and was left with no OS stuck in bootloop with no way to get into the bootstrap recovery we had...was without device for 3 days until I could get to a coworkers laptop!! Lol!!!) But the stress goes WAY down after you've restored device once or twice and have the tools at the ready with basic understanding of the steps at least
And as for drivers, I apologize for not warning/informing about that. I forgot that you mentioned you had multiple driver packages downloaded and i was going to clarify which to use(on a Linux setup you don't need drivers and it been a while since I used windows for my device so drivers aren't usually on my mind lol) I think a lot of people use the PDAnet drivers. But if you are connected to internet and just put device in fastboot mode and connect to computer, I think it will automatically find and install the correct drivers needed for fastboot/adb access.(the toolkit can also be used to install correct drivers I believe)
And don't worry, I wouldn't call using toolkit the "cowardly way". SOME people detest/despise use of toolkit since they think it takes away from learning and understanding how to do it without a toolkit. But when you use a toolkit you usually see command prompt correct? (Or at least a setting so you can SEE what it is running as far as commands) so you get to see what its doing, which helps beginners start to grasp the concepts of what it is doing.
Trust me, if you can use the toolkit correctly, you can easily transfer that knowledge to just using fastboot or adb commands.
by the way, fastboot is what's used for factory image restore. ADB is for pushing/pulling files, taking logs, sideloading a ROM/gapps zip that isn't on device, taking/restoring adb backups of system and or data, things like that. Think of adb as the "taker and giver". And fastboot as the "img installer/booter"...imgs being anything from system img files, to data partition img files, boot.img(aka kernel), recovery.img, bootloader update img, radio imgs. Things like that
The reason the knowledge from using toolkit easily transfers over to using just straight up fastboot for example is because of how they word the choices and menus. You will see it says something like "use fastboot to flash new recovery img", which the fastboot command for that in command line equates to "fastboot flash recovery "NameOfRecoveryImage.img" "
(With no quotes of course, and replace "NameOf...." With the actual file name of the recovery.img you have downloaded, and you can rename the downloaded recovery img file to something easier to type out if you want to also)
Basic structure of using fastboot command would be as follows:
fastboot[space]command[space]partitioname[space]filetobeused
Which after used once or twice is very easy to grasp basic usage
So are you able to at least boot into OS now? Also, make sure if you are trying to flash a KitKat ROM, that you install the 2.7TWRP recovery, anything earlier won't work correctly for 4.4based ROMs.
Again, any trouble feel free to ask.
(And apologies for the long rambling posts lol)
yes. i am in the OS now.
what gave rise to my troubles in the first place is that i've moved my residence. all my devices recognize my new wifi, and proceed along their merry way.
my gnex is another story. it recognized my wifi, shows me as connected, but nothing at all can actually access the server. i tried factory reset, nothing. then i was going to install a new rom, figuring something was corrupted. then my 2 year old took over!
so i am in the OS, but still cannot access the server. so it must be on the server side i figure. not sure how to fix this, but when i have some time, i'll do some looking around. i am going to try to access a different wifi network later on to see if at least it is not my device.
again, thanks for your help my friend.
boathead said:
yes. i am in the OS now.
what gave rise to my troubles in the first place is that i've moved my residence. all my devices recognize my new wifi, and proceed along their merry way.
my gnex is another story. it recognized my wifi, shows me as connected, but nothing at all can actually access the server. i tried factory reset, nothing. then i was going to install a new rom, figuring something was corrupted. then my 2 year old took over!
so i am in the OS, but still cannot access the server. so it must be on the server side i figure. not sure how to fix this, but when i have some time, i'll do some looking around. i am going to try to access a different wifi network later on to see if at least it is not my device.
again, thanks for your help my friend.
Click to expand...
Click to collapse
what security do you use on your router? if WEP try changing it. the gnex has issues sometimes with using WEP secured WiFi AP's
also, if using a 5ghz network, I can only get mine to connect to that on channel 153. there are only a certain number of 5ghz channels supported.
might also want to just try forgetting WiFi network and re add?(if it restored the access points by any means including Google backup/restore)
and make sure your router isn't rejecting the Mac address for some reason(and some people will suggest reboot of the router to see if that helps fix it, which I've seen fix many connection issues)
well, my device works beautifully....everywhere except in my house.:crying:
as much as drivers befuddle me, routers do even more so. it must be a router issue, right? my device connects to google elsewhere. and all my other devices connect to google here at home. maybe tomorrow i'll try the router's live chat to see if i can get some help.
boathead said:
well, my device works beautifully....everywhere except in my house.:crying:
as much as drivers befuddle me, routers do even more so. it must be a router issue, right? my device connects to google elsewhere. and all my other devices connect to google here at home. maybe tomorrow i'll try the router's live chat to see if i can get some help.
Click to expand...
Click to collapse
what type of security are you using in the router setting? WPA? wep? none?
what model router are you using?
is device connecting to internet and just not Google servers?
is device connecting to router at all and just no internet access?(meaning when you are in WiFi settings, and choose network does it show obtaining IP address and then connected? or just never fully connect?)
I've had similar issues in past and might be able to help with some more details
ashclepdia said:
what type of security are you using in the router setting? WPA? wep? none?
what model router are you using?
is device connecting to internet and just not Google servers?
is device connecting to router at all and just no internet access?(meaning when you are in WiFi settings, and choose network does it show obtaining IP address and then connected? or just never fully connect?)
I've had similar issues in past and might be able to help with some more details
Click to expand...
Click to collapse
wpa2...but i've even disable all security to see....i've disable firewalls...nothing. it is an arris router that time warner cable provided when i moved to my new place.
and i my phone does show me as connected to my network...just can't get into google. and the phone works just fine at my work. as you know, i've been through several roms and an entirely new OS...so it cannot be the phone...can it?
been through this entire threads, and no joy.
http://forum.xda-developers.com/showthread.php?t=2110225
if you have any ideas, post away. i will be away from access to the internet for a few days, so i won't even have a chance to check in here, but any info in the meantime would be most thanked.
boathead said:
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
Click to expand...
Click to collapse
my samsung s5 had the same problem. i wiped out everything and it says i have no os no nothing. i hope if anyone can help, i will be pleased.
the only question is that "how can i get an os and get my phone working"
ashclepdia said:
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
Click to expand...
Click to collapse
The same thing happened to me right now, while I was installing CM13 in my Lenovo Zuk Z1. I took a backup from TWRP and copied the same to my pc. Then I wiped all the data from my phone using TWRP. Then I plugged in the Usb back to copy the downloaded files of CM13 to my phone but my pc is not showing the Internal Memory of my phone. I am so freaked out right now. I dont have an OS in my phone and I am unable to restore what I backed up. I am just stucked in TWRP. Guide me through to install CM 13 or atleast revert back to where I started. Any help is appreciated.
Hi all!
Some days ago I urooted my TV android tv box with superSU and then I restarted it. From that moment when I plug the device it only reach the T9 logo (not the android one) and don't go further.
I've tried different ways to try to unstuck it, but nothing has worked.
I tried:
- enter recovery boot by holding the button in the av hole -> nothing happens
- install new firmware with adb sideload with both ubuntu and windows 10 -> always get errors (often error: closed, sometime other errors that at the moment don't remember)
- install new firmware with sd card using SDCard Installer -> the device doesn't boot when the sd is inserted
Moreover, with adb in ubuntu sometimes it recognises the device and I can enter the adb shell (but obtain errors when try any tipe of command), and sometimes don't (after adb devices I see list of attached devices: ??????????????? offline)
Now I'm thinking to try to install an ubuntu like on an usb pendrive...
I will be very grateful of any help/suggestion to how to revive my device :fingers-crossed:
Thank you!!!
Does this happen to be a pendoo model? I have a pendoo x10 MAX and i actually simply just installed supersu while it was rooted. Since then, I haven't gotten this thing to boot. Just stays on the boot screen the entire way. I wiped in recovery, knew that'd do nothing. I just wanted a root MANAGER. I tried Magisk, my favorite.. no go.. so then I went a bit old school.. so I tried ChainFire's SuperSU.. and THAT updated the SU binary! It said it succeeded.. it asked to do recovery install or normal install.. on phones, I've always done normal.. so I chose normal. Plus.. this thing has no custom recovery. I found it on Amazon. Overpriced, but great with the controller it had. It looks like I'll need a replacement and maybe a request to ask this guy if he could possibly NOT use something like KingRoot/KingoRoot/AmaraRoot or ANY One click root tool.. they just cause more bloatware, inciting boot issues and problems within the Android box itself. These One Click Root tools are out of control. It's to the point where I need to find a way in to adb and find the firmware for the latest version of this thing... X10Max from Pendoo.. I have not found a thing anywhere regarding firmware, and their website is ****. NOTHING *anywhere* on these things.. hell I'm about to return it as I bought it for $72. I have another one, same model.. wondering if the root method was different. About to boot that up and find out. I'll even swap the board. At this point.. he rooted it.. the WRONG way.. you can MOUNT THE /SYSTEM PARTITION IN RECOVERY. THIS IS ANDROID 9 we're talking about--the recovery supported by API v3.
This can and should have a TWRP custom recovery. If none exists, don't bother. As long as you can mount /system then you have a chance, at least, to root the damn thing.. which is why I'm still messing with it. I have another two weeks to return it. I'll give it another couple of days before I call it off and just switch out the good board for the bad one, return it, then return the other one and just use it until I find a way to use a custom recovery on this thing. There has to be.. unless there is no firmware available in sight (for an RK3318 or 3328, can't tell.. recovery mode says 3328, model name says RK3318. I see no difference at the moment aside from processor naming at this point--maybe speed?)
I'm still a nub with Android TV boxes so don't hold it against me for updating the damn root binary. If I could find a way to just reinstall the entire firmware and delete all previous stuff, I would. It would be worth it to learn. I would then mount /system in recovery and soldier on.
One little issue with this thing.. there's only one USB port that actually works. Same applies for the same exact product, a replication of the same thing.. was a "replacement" that still have/has the same qualities.
I've ranted enough. I vote more research into RK33xx processors and possible custom recoveries. I'm about to look for it based on only the device itself.
Note: Been stuck at boot screen ever since the binary was updated. I felt it was necessary to have a boot manager. I don't know where to even find the firmware. Can.. anyone point me in any direction? Something that MIGHT work on this thing? Android 6 or 7 would even suffice, return or no return, as "stuck on boot screen" will be my complaint. That's.. the actual complaint. I can't just *flash it* like the old days.. and maybe the original Android 9.0 firmware would suffice.. I don't know, but Pendoo.. wouldn't that be preferred?
You will need an SDcard to recover this box. I think the T9 32GB 4GB rom will do the job since its a cut down version.
Make a update SDcard and pop it in and power on the box. It will start the recovery on its own.
hello, sorry for my English I live in France I would have a question about the box: TV T9 RK3318, 4gb / 64gb. the problem is that the time is desynchronized on restart and creates problems to connect to applications when the time is out of order, I tried everything changed the time zone to deactivate and entered the time Manual it goes out of order all the time . is there a custom version or a version 10?
Very cook did I checked this out awhile back alot of good information that's for your contribution
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.