First allow me to apologize for my clumsy English and this long boring post
I m a total noob when it comes to android, recently I bought a DHD and I would love to root it
However the first thing I would like to be 100% aware of is the worst case scenario
I m a PC technician so it would be very kind of you if you answered my Q by comparing the DHD to a computer
If you own a new laptop then u can mess with OS as much as u want, then u can recover the laptop to its factory defaults by using the recovery function
-in some laptops the OS has to be healthy and you'll have to able to log into your account in order to restore the system
-in some laptops you can restore the OS from outside the OS using a hot key cause the recover partition is a standalone partition and hot key is managed by a software which works in a layer above the OS
-in some laptops its even better! u can create recovery disk so you mess with the OS and HDD itself then you can restore the HDD to its factory defaults
-the only thing that might force u to go for a hardware solution is when u mess with CHIPS like the BIOS
if something went wrong while you are upgrading that chip u wont be able to fix it at home with any software but you'll have to take the chip out are reprogram it using a EPROM programmer
After this boring long introduction here comes my Q: how bad can I damage my DHD? I've read the word "brick" here and there, is that the worst case scenario?
I know less than nothing about the internal architecture of mobile phones but I always imagined old mobile phones it as a Read-Only chip that loads the OS into a RAM where u can mess as much as u want and once u reboot you are back to life
I m not sure if I m making any sense so I'll try to compare my Q to the iPhone
you can mess with the iPhone as much as you want (as long as u don't use a tool that upgrades the boot loader) and you can always restore the OS from a (higher) level using a third party application
Same thing with BBs right? u can always (inject) the OS back into the device using an executable OS file
What about android devices?
I apologize again for boring you
Thanks
Rooting wont necessarily brick your phone or damage it as all as when you root your phone you are basically gaining 'admin' rights on your phone.
The danger of 'bricking' or damaging your phone comes in when you start to remove the security off your phone so that you can flash a custom recovery, new radio or kernal.
This a very basic and minimalistic answer to your question but that is basically the just of it.
If you follow all the instructions to the point nothing should go wrong and if it does there is allways someone that can help
Running a PD98IMG.zip or RUU will revert your phone back to stock
Oh and once you have performed radio and/or eng s-off there are also very specific instructions to revert this back to stock over on the development section aswel.
Good luck!
RaymondErasmus thank you very much for your most-welcomed answer but can u be more specific?
tbh there are loads of tutorials all over the Internet but I m looking for simple in-depth details, in other words I m trying to understand which parts of the phone I m messing with
Regards
Okay, I'll try to explain it.. These phones have @secuflag, which is written deep in the internal memory. It tells your phone it's security state, S-ON or S-OFF. When security is off, your device's internal memory becomes read/write instead of read only. It allows you to flash ROMs (OS package) and do other exciting modifications to the software.
When security is off, you can do literally anything, even delete your phone's bootloader, so that it becomes just a pile of hardware with nothing to boot. That is called a brick. When you have the bootloader intact (always), you can recover your phone from any state. Usually people have ClockworkMod installed, which is a custom recovery application. It allows you to even format the internal memory of your phone, and then flash anything you want. Without ClockworkMod you can still go to bootloader no matter what, and send a whole OS into the phone using RUU USB connection.
Rooting itself does not turn security off, but S-OFF obviously does. Without S-OFF, you cannot hurt your device in any serious way.
jkoljo your answer is just awesome! Kiitos man!
This is exactly the type of answers I was seeking for, I was right about joining this great forum
Can you share more details? any diagrams to explain the relationship between the components/registers of the internal memory? and more details regarding the process of booting up in Android phones?
Thanks again man
Sure mate, about the boot procedure first:
The ARM SOC gets powered up
PBL (primary boot loader) starts running. It sets up partitions, for example, and initializes hardware. It executes DBL.
DBL, device boot loader checks bootloader (hboot) in case of corruption and such things, then executes OSBL
OSBL, operating system bootloader, hboot, sets up rest of the hardware system. It checks secuflag and sets internal memory accordingly, for example. It has the ability to read and write firmware. Then it basically executes linux kernel.
Kernel starts running, initializes your system (drivers etc) and starts booting up Android.
For end user, hboot and recovery act as the base of the device. Hboot provides access to various partitions like radio firmware, and clockworkmod recovery provides extensive control of /system, /data and such system related partitions. Hboot has the ability to boot up clockworkmod, regardless of the state of the system (corrupted and broken / fully healthy).
You might be interested in this.
For very extensive information about low level stuff, check this out.
For the record, seraph1024 posted a wonderful thread that helped me to understand some stuff
[Newbie Guide] adb/fastboot/bootloader/android 101
In Cyanogen Mod 7 version 12 is the apps2sd automatically enabled or do i need to create a partition on the sd card?
and if i need a partition then what type of partition do i need ext 3 or ext4??
rooting wont harm your phone if you followed the rooting process religiously
Related
Problem:
a. CID Locked phone from Latin carrier but attempted upgrade anyway.
b. Did not backup original ROM before attempting upgrade (original ROM impossible to get on internet).
c. CID Bypassed and attempted upgrade from WM5 to WM6, USB cable disconnected at 16%!!!
d. As consequence, phone stuck on splash screen when turned on (must pull battery to turn off), I'm only able to force it into bootloader mode (connects to PC but no activesync connection). No cooked or official ROMs work (invalid vendor id message because phone stayed CID Locked) and as I said, original ROM impossible to get on internet: B-R-I-C-K-E-D!!!
What I attempt to do:
a. Get a hold of my friend's new, untouched, same carrier, same original ROM, same brand, same model WM5 phone.
b. Backup my friends phone with Sprite 6 (with Device Upgrade Mode) creating a self restoring backup file (backup.exe)
c. Use said backup file on my bricked phone to restore original factory/carrier ROM.
Aproach:
Connect the bricked phone in bootloader mode to the PC and run the backup.exe file that Sprite Backup 6 made of my friends phone.
Main question:
Does said backup.exe file need an activesync connection to connect to the device (somethin bootloader mode can't do)? or is it able to run with device on bootloader mode? Like many RUUs outhere.
Why I ask:
I don't want to cash out 30 bucks for Sprite Backup 6 only to find out it wont help me.
Other questions:
Has anyone else done these?
Does is sound plausible?
Other backup software that may do what's needed?
Sprite backup wont help :-(
sorry for bad news
BTW. it might be usefull for everyone to write what device U have, and/or post it to that particural thread.
why?
phsnake said:
Sprite backup wont help :-(
sorry for bad news
BTW. it might be usefull for everyone to write what device U have, and/or post it to that particural thread.
Click to expand...
Click to collapse
Does it need active sync?
It's an HTC Excalibur
I posted on my device's forum about the bricking and someone told me I should have backed up first with Sprite. Why would a Senior member say that if it doesn't work?
I appreciate your fast answer, but would you kindly care to elaborate?
DOnt know, but Sprite is for backing up installed SW & date. Anyway how do U expect to run EXE, if phone is bricked? It needs OS to be run on device (or thru sprite srvr on PC & async connection). RUU is different thing. RUU directly overwrites DOC and that for doesnt need async.
OK.. got it... then...
I've read many many times these golden rules:
"Backup your original software before you upgrade." And, "If you brick your phone you can only flash your original ROM."
In fact I've been scolded (politely) in all the posts I've made about bricking my phone for not backing up the original software before the upgrade.
What software does this if not Sprite? How do people back up their original ROM before the upgrade in case of bricking?
As I understand, if I backup the original ROM of my friend's Excalibur (which I said in this thread, is a clone of mine: same carrier, same OS, etc.) with the right software, I'll be able to flash it onto mine and unbrick, right?
I suppose I have to make an *.nbh file of my friend's ROM, replace it in an extrated RUU, and run the *.exe
One last question, are you sure the *.exe made by Sprite 6 works different from the RUU's one? I've read in the support section of Sprite's website when refering to self executable backups: "they can restore your device after a Hard Reset without having to reinstall sprite backup first" and "if your device doesn't boot after a ROM Upgrade"
As mentioned Sprite only backs up data: system setting, your files, databases, registry, and so on. It doesn't back up the ROM. This is generally only recommended in case the flash of the new ROM erases your data.
No idea how to make a backup of the original ROM... although I'd like to know.
If you will pm me or find me on MSN/Live IM @ ([email protected]) I will help you to determine if your device is truly a brick. I have a good reputation in the Kaiser forum & have successfully "unbricked" over 50 devices.
My main concern is that you don't do too much more damage in your state of panic. Please try to refrain from trying to many things.
Again, email or PM me to remind me, & I will have you pr walk you thru a few diagnostic tests. Because I don't know what device you have, you didn't mention it, it may take a little time ( a day or so to locate & disassemble your device SPL & OEMSBL) but I am confident I can resurect your device.
There are also tools available that WILL allow you to dump another device ROM & then reconstruct the raw data & repackage it into a flashable version. Slight modifications may be necesary, but again, I think we can get through this issue. It sounds to me like a bad Memory Block, but I'd like to confirm that before jumping into the "let's fix it" phase.
If reflash is required, we will have to dump to raw data, pack that into a .nbh or .nb0 & then we can modify a RUU to call on that nb file for reflashing. It is a bit of work, but there is a 60 to 70% chance that it won't even be required & a simple memory block flush will be sufficient.
Great!! Gsleon U Rock!!
OK... I'm adding you to MSN right now, I'm new to this and besides unbricking my phone (HTC Excalibur) I'm eager to learn everything about modding, upgrading, etc. mobile phones.
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
I don't think there is a company that provides such a service especially if we take in to account that kaiser/tilt is a 3 year old device and the android port is not official. There are plenty of topics in the forum describing how to replace winmo with Android. You don't have to be a hacker to run Android on your phone. Just read the stickies and you wil be able to flash ityourself in no time
There are phone dealers out there (in the USA anyway), that will do this for a fee on the Kaiser, but trust me, with what has gone into the development of this, almost anyone can do it. Save yourself the money and try it yourself. The worst I've heard about is a mis-flashed phone needing some master reset.
The question is who?
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Henrykjr said:
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Click to expand...
Click to collapse
Listen HenrykJR there are about dozens of android builds on this forum + many different versions of two kernels, not all of those will work correctly for you. You might experience different issues with one setup but the other will work correctly for you. So even if there was a company that could flash it for you, you might end up with an unstable device. Also how could a company gain knowledge on flashing android builds to a phone that was originally shipped with windows mobile??? You seem to be looking for Nessy....in woods.
Your best bet now is to find someone in the forums to help you flash your device....maybe even use skype to show you how to do it. It really isn't that hard.
Hehe, i don´t think you´ll find a Company that will do it for you. Maybe you find some guys that do it for Money (me to ). But if you spend a little time with reading through this forum you could do it yourself and save the money.
Preparing:
1.) You need a SD card (mandatory for android on Kaiser). And you need a Google Mail Account for syncing your contacts etc. and access the android market.
2.) You have to "unlock" your Phone (with HSPL/HardSPL). Only after that you are able to flash things (Cusom WinMo ROMs, Radio, Android) to your Kaiser. So read through this guide and follow step 1-4.
3.) Now you have an unlocked phone an you should be able to flash everything. And the first thing you flash should be the latest "radio". The "radio" for Kaiser is similar to the BIOS for your PC. Like the subsystem and responsible for GSM chipset etc... So look & read in this Radio-Thread, download the latest Radio (it is 1.71.09.01) an follow the guide "Flashing Radio from microSD"
4.) Now your Phone is up-to-date and ready for flashing Android (or WinMo custom roms). YOU NEVER HAVE TO DO THE STEPS 1-3 AGAIN! Your Phone is now completely prepared!
Flashing Android:
For Android on Kaiser you always need 2 Parts. The Kernel (this part initialize the hardware so its similar to "driver" on PC) and the Built (the Android OS itself). But Both should work together so you´ll may find in some kernel suggestions in Built-threads because not ever kernel work with every built. For your beginning i whould suggest you some things:
First the kernel:
DZO is the most popular (the father of android on Kaiser) Kernel-Developer for Kaiser. So go to his repository and download "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh". Because Vouge and kaiser have almost the same hardware we all could use this kernel. But everyone have to modify this kernel to make phone related optimizations. You can do thy by hand (not recommended for you) or with a tool called "Atools". This tool is writthen in "Python" so mac and linux user could use it too. But you need to install Python. But that is all described in the Atools thread. Read through it and follow the guide.
Modifing Kernel:
We will only modify the madatory things. Not more at the moment...
So run Atools, klick on the "folder" Button and load the "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh".
Device: "Kaiser" should be checked
Resolution: 240x320 should be checked (native resolution of Kaiser display). Everything else will give blurry optic.
Version: "Froyo" should be checked, because we will flash a Froyo built (thats android 2.2). If you want to flash an older built like a Donut one (1.6) you have to modify & flash your kernel again.
Panel Type: Try "auto" or "1" first. But if you have a fuzzy screen or artifacts you have to try out which paneltype fits best for your device. HTC has built in 3 different displays in the Kaiser and the only way to find out which one is builtin is trial & error.
Keymap: Depends on which hardware keyboard layout you have. Here in Germeny i have to use "qwertz".
We leave the other options as they are an klick on the "Disk" button to save our modificated kernel now. it save it as "KAISIMG.nbh".
Now we need the Built:
I suggest "Fat Free Froyo" at the moment. Fast, stable, an looks good. So go to this thread and download "ODEX DOWNLOAD RLS5 ALL LANG-ODEX" on the bottom of the post.
then unzip/unrar this file...
Flashing your first Android:
1.) You should have a fat32 formatted SD card
2.) put the Kernel (the modified KAISIMG.nbh) to the root of SD card
3.) Create a folder named "andboot" on SD card
4.) Put the unzipped file (androidinstall.tar or .tgz) in the folder "andboot"
5.) Remove SIMcard and any cables from phone and put the SD card in your phone. Battery should be 50% carged or more...
6.) go to bootloader-mode (press and hold camera button and powerbutton). the KAISIMG should be loaded and it will show you "press powerbutton to update" or something similar. Do that... Now a progressbar will appear. When it is at 100% wait a few seconds an then pull the battery. Wait 10 seconds an insert it again. Voila! You flashed your first android kernel!
7.) Now we have to install android itself. So Power on the phone. In the moment when you see small white text on black background you have to press and hold the d-pad button. This one in the middle. Now you get in the install menu.
8.) Leave the options "System on nand" and "DATA on nand" as it is. Navigate to "install system" an press dpad. It ask "format system" and "format data". Both "YES". after this procedure you enter the menu again. navigate to "quit".
9.) Yeah! The first Bootup of Android! The first bootup takes longer as the following ones because now the system prepares for bootup and do a lot of optimisations. Even if you enter the lockscreen you should give it 10 minutes time to finish this optimization process in backround.
10.) Finish! You have flashed your first android completely! Now you can play around and make your settings. Remember: You have to sign in to your google account befor you can access the market or syncronize your contacts etc.!
Sounds more complicated as it is. Try it!
And if you´ll dig in deeper in this stuff you have to read here! Especially the Stickies/Refs/Tutorials! We´ve all done that!
have fun!
Henrykjr said:
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
Click to expand...
Click to collapse
Brother, You can do it yourself, I can assure you. Regarding any ambiguity, you can contact me through PM. (I can guide you complete on voice over skype / msn). Its a TIDEOUS job but EASY to do since there is no MEANS OF BRICKING your kaiser (unless you flash something else than what u have do to install android).
I am here to help you in this community. And you can do this thing yourself.
Your device is At&t Tilt. The bad thing about installing android is getting a RIGHT kernel that suits your LCD type and enables wifi in the android build u install. (maybe in 1st try, maybe takes almost 10 tries like it happened for me)
Hey,
I've got a friend that has a s8500, the screen broke and i changed it. By the time i gave it back to him he had forgotten the Phone Securty code he had setup. The only thing i want is a way to recover the data before the reset.
Is there any way to achieve that? Or is there any way to reset/get the code ? I've been looking into the FLOCK thread but im afraid it will lose the data after the flash.
We also contacted Samsung and they said the only way to reset that code is with a hard reset which will make the data being lost.
Can i in recovery/download mode get the data? The most important thing is the contacts/photos.
Thanks in advance.
w1ckedz said:
Hey,
I've got a friend that has a s8500, the screen broke and i changed it. By the time i gave it back to him he had forgotten the Phone Securty code he had setup. The only thing i want is a way to recover the data before the reset.
Is there any way to achieve that? Or is there any way to reset/get the code ? I've been looking into the FLOCK thread but im afraid it will lose the data after the flash.
We also contacted Samsung and they said the only way to reset that code is with a hard reset which will make the data being lost.
Can i in recovery/download mode get the data? The most important thing is the contacts/photos.
Thanks in advance.
Click to expand...
Click to collapse
No idea about the FLOCK thing, i think it's to unlock SIM-LOCK or freeze and not the phone.
The photo are recoverable with android, not sure about the contact (i don't know where they are stored in bada).
In short, you need to boot an android recovery (see the android dev on bada section, i can also provide more detailled instructions), mount bada user partition and then copy paste what's inside on SDcard.
It need an sdcard, a SD fota, multiloader an android kernel and adb (android debug bridge, free software anywhere on the net).
No data will be lost if you do it (if you are on bada 2, else i don't know, and phone will still be locked).
BenzoX said:
No idea about the FLOCK thing, i think it's to unlock SIM-LOCK or freeze and not the phone.
The photo are recoverable with android, not sure about the contact (i don't know where they are stored in bada).
In short, you need to boot an android recovery (see the android dev on bada section, i can also provide more detailled instructions), mount bada user partition and then copy paste what's inside on SDcard.
It need an sdcard, a SD fota, multiloader an android kernel and adb (android debug bridge, free software anywhere on the net).
No data will be lost if you do it (if you are on bada 2, else i don't know, and phone will still be locked).
Click to expand...
Click to collapse
Thank you, i had forgotten that i could just boot a costum recovery. Need to do some research on the contacts location tho since it's really the most important data i need to recover. Thank you again.
We are looking for technical help with RockChips RK3066 NAND driver.
We have several in-field customers that would greatly benefit from the RockChips NA
Code:
ND driver update.
Because we need the RockChips NAND update fix, we have to proceed with a low-level format of the entire storage media, leaving the device helpless for several minutes.
We understand we would need a specially made boot & kernel ramdisk working without any storage media and also access to low-level NAND driver functions.
We understand we would also need to update bootloader from 1.22 to 2.25 ( which is a pretty big deal on its own ).
This is all to be done "live" without usage of USB connection.
We understand this is a quite challenging update.
We are first looking into whether a very specific technical reason would make this completely impossible (e.g.: the relevant code being in mask ROM for example )
Any help answering this query is very appreciated.
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.