Related
Welcome
I bought a new tablet Z3 compact (SGP611) with KitKat and after a few days I decided to put new rom of Lollipop via CyanogenMod 12 Nightly ROM. Because I'm outsider with the android matter, I have visited and read dozens of pages in search of an intelligible instructions and most were unclear. First I unlocked bootloader and the next thing was to install a custom recovery with ClockworkMod (CWM), and here I lost. At this moment I have a dead tablet (no reaction on the start button).
What I did I took from this page: .android.gs/install-cwm-recovery-on-sony-xperia-z3-compact
On your computer download the Advanced Stock Kernel
Save this file on desktop and apply the steps from below.
Enter your Sony Xperia Z3 Compact into fastboot mode: first turn off your phone; then press and hold Volume Up key while plugging in the USB cord for establishing a connection with the computer.
Good; now your device will be entered in fastboot and also connected with your PC.
From your computer, from Fastboot folder open a command prompt window: press and hold Shift keyboard key while right clicking on any blank space.
In the cmd window type “fastboot flash boot boot.img” – replace boot.img with the file name you need to install.
In the end, on the same cmd window enter “fastboot reboot”.
That’s it.
Click to expand...
Click to collapse
"
The difference is, I save this file to Fastboot folder C:\Program Files (x86)\Minimal ADB and Fastboot, and then I wrote in command prompt window
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
fastboot reboot
That’s all what I did? Question: what **** I did? Now I have 270 g electronic scrap.
Is there any chance to put this tablet to live? Who can do this?
Can anybody write, or show me a link to good instruction for doing this?
Sony Xperia Z3 Compact (phone) is different than Sony Xperia tablet Z3 Compact Wifi 16GB (SGP611)
Instructions for installing CM12 is basically here http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534 ( To install CyanogenMod 12 nightly )
Just change the rom scorpion (Z3 compact tablet lte) by scorpion_windy (Z3 compact tablet 16GB Wifi) : http://download.cyanogenmod.org/?device=scorpion_windy
maybe it's just stuck but still turned on. try using the reset button located under the sdcard slot cover (it's a yellow 'pin' labeled 'OFF' in case of the SGP621). push it for about 3 seconds then try turning it on again with the power button and see if its still alive.
I think u used the the recovery of a Sony Xperia Z3 Compact (phone)
Try to flash the stock kernel and rom, it is : 23.0.1.A.0.167
Than unlock bootloader again, (i did it with unlock code givin from sony)
than flash TWRP Recovery/Kernel
From there u know what to do, Flash Cyanogenmod 12, Scorpion_windy,
Szturwal said:
At this moment I have a dead tablet (no reaction on the start button).
Click to expand...
Click to collapse
@Tekodrink: Seems more like he's not getting any life signs whatsoever - how would you flash anything on some device that does not respond?
sandrap said:
@Tekodrink: Seems more like he's not getting any life signs whatsoever - how would you flash anything on some device that does not respond?
Click to expand...
Click to collapse
Try to put in fastboot mode, with adb fastboot
if it still doesnt something i dont know it anymore
After sixth days, I wanted to send tablet to Sony service. I put it to the box, and wanted to wrap with paper, when I fill some vibration. I took it off, and tablet started to react for pressing start button. Electronic devices are unpredictable. I flashed system with Sony flash tool "Emma", and is working now, with old KitKat. I give up, and will wait for Lollipop from Sony.
Szturwal said:
After sixth days, I wanted to send tablet to Sony service. I put it to the box, and wanted to wrap with paper, when I fill some vibration. I took it off, and tablet started to react for pressing start button. Electronic devices are unpredictable. I flashed system with Sony flash tool "Emma", and is working now, with old KitKat. I give up, and will wait for Lollipop from Sony.
Click to expand...
Click to collapse
Lollipop for Sony good old times.
After upgrading to CM 12.1 everything was just fine. Got my tablet to charger and left it there for a while. And then i saw that i was looping.
It's trying to enter recovery (TWRM) "or something like" and restarting.
I' sitting on forum for 3 days already. trying to get some information and did lot's of things. Nothing helps.
Can anyone help me with this somehow? I'm almost crying and losing it (not really, but that what i feel inside)
Please. Any help. I think I've read all forum about this thing.
Thank you.
Do you have the real TWRP (i.e. not Safestrap!) & an unlocked bootloader?
don't think so. or better say i'm not sure about it. how can i check?
Edit:
i can run adb and after command "adb devices" it shows serial number and status: recovery.
i can use the command adb reboot-bootloader which puts me in fastboot mode. but then i try adb devices and have nothing there.
also, any command like "fastboot...." gets me to "waiting for device" and nothing more.
I tried two different computers. all ports. all cables that i've found.
Edit 2:
also after command "adb shell" i ca see "~ # ←[6n" and i can put there only reboot command
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Cl4ncy said:
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Click to expand...
Click to collapse
Also verify you have a Kindle HDX ... not HD or generic Fire.
the fastboot command got me still only 1 message "waiting for device"
Tried to install drivers. While looping, in device manager, i can see "Fire devices: Android composite ADB Interface"
and "Portable devices: MTP USB Device"
If i enter fastboot mode, gets me to "Other devices: Unknown device" and i just cant figure out how to install the drivers. Tried to download some stuff. plugged, unplugged.
Edit:
After some work done with drivers, i input adb kill-server and adb devices and get "Serial Number Unauthorized"
So maybe i should change word "work" to "messing" with driver
what do i do from here... is there any live chat for it maybe? or i can call someone?
Well, do you have the real TWRP or Safestrap? Can you enter recovery?
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Still haven't answered Safestrap or native TWRP query (you should know). Do this:
- long press power until device shuts off
- restart device with power button (only)
- detail the 1st, 2nd and 3rd screens you see
If you do not have native TWRP (with unlocked bootloader) you likely borked your device with the installation of CM 12.1. Generally not repairable.
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Cl4ncy said:
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Click to expand...
Click to collapse
To check if your bootloader is unlocked (assumes you previously unlocked and still have the prerequisite software installed on host):
- power down device
- press vol-down + power; release both keys when "[fastboot]" prompt appears
- tether your device
- open a command prompt (assuming Windows)
- issue command: fastboot -i 0x1949 oem idme ?
- you will only get a response if bootloader is unlocked
If the (Windows) host displays "<waiting for device>":
- press <ctrl>-c to break wait
- start device manager (different window)
- located device with explanation mark (likely under "portable devices")
- right click -> update driver software -> browse my computer... -> Let me pick...
- select driver from list (ideally one that contains the words 'fastboot'); might have to try a few
- reissue above command
Bit of a PiTA ... might be easier to simply try the one click unlock tool as there is no additional risk to your device. It will either work or not.
I guess i'll check it only next week. Leaving all this things for the weekend.
I'll keep you updated guys.
Anyway, i really appreciate your help! Thank you so much for helping
same problem
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
stephio said:
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
Click to expand...
Click to collapse
I assume you have an unlocked bootloader and were running 'native' twrp (not Safestrap) when the problem occured. Unfortunately, there is no known 'quick fix' recovery from this failure scenario (boot looping on teamwin spash screen) as you have tried to reinstall twrp without success. Someone very talented with android might be able to unravel the problem. Best guess (and it is only a guess) is the recovery partition became damaged to such an extent it the contents can not be replaced without performing a low level format/reset of your device.
Some curiosities:
- Android 5.0.1 and CM11? (impossible combination)
- TWRP freedom? (not supported on HDX)
Are your certain your device is a HDX and not some other model?
same problem
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
stephio said:
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
Click to expand...
Click to collapse
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
same problem
EncryptedCurse said:
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
Click to expand...
Click to collapse
I searched the web and I have definitely amazon kindle fire HD 8.9 because even his appearance differs from the HDX 8.9.
no I do not really think the problem comes from the data flash HD 8.9 (wikicyanogenmod) because I flashed the data after doing a factory reset without actually knowing that this would pose a problem with amazon tablets.
the tablet was working well but I was unable to connect to the wifi. I thought it would be nice to change rom and install a suitable and stable rom for my tablet, but my operation I was surprised because I had never heard of this kind of problems caused by an factory reset
Hi Team,
i am using Lenovo ZUK Z1 , morning today, after restarting the phone manually, device has gone into endless restart loop, i can boot onto recovery menu as well as fastboot mode, from what i have read so far i have to flash Factory image, to be able to bring this to a usable state, i would like to tell you that i cannot get the bootloader to unlock since OEM unlock option in developer option is disabled, i dont have any custom recovery installed, neither can i use adb commands since USB debugging is disabled, i have tried factor reset but the phone still continue to reboot and optimizes apps, what should i do to get out of this?
I would like to apologize if i have failed to convey my point properly, also please pardon my ignorance, since this is my very first question on this forum
Thanks in advance.
I was trying to flash lg-k350n with LineageOs and make a whole bunch of idiotic deeds, so currently I'm felling like dying is the best option for me.
1. I've used this tutorial: .getdroidtips.com/install-custom-rom-using-twrp-recovery. It clearly says that this ROM is for Android 8.0 Oreo, while mine is Android 6.0 Marshmallow. Nevertheless I've downloaded ROM lineage-15.0-20170913-Unofficial-MT6735-64-bit.zip. For some reason TWRP mentioned here getdroidtips.com/lineage-os-15-lg-k8-8-0-oreo/ did not wok for me but I've googled a bit and found something called TWRP-recovery-for-LG-K8.img which worked (not by fastboot flash TWRP-recovery-for-LG-K8.img since this TWRP appeared to be to big but simply by fastboot boot TWRP-recovery-for-LG-K8.img).
So I just did:i
turn on debugger
turn off oem lock
adb boot bootloader
fastboot boot TWRP-recovery-for-LG-K8.img
Feeling happy that TWRP loaded nicely I had not done any backjup and just wiped system as suggested here: lineageos.org/devices/h990/install. Then I've tried to installl the Android 8..0. ROM with obviously did not work. And I've got left with a TWRP working and then I've put the last needle in my coffin - I've rebooted hoping that some hard reset or recovery will fix things for me.
So now I have a phone which I'm able to put to recovery, but it does not recover anything. The phone just go dead after such a recovery.
I cannot put it into fastboot mode, if I could, I would just run 'fastboot boot TWRP-recovery-for-LG-K8.img' and at least had a chance to google a bit for maybe a vanilla ROM or anything working, which I could've later installer.
I've seen that there is a way to put the phone into download mode when it will download stuff from S/W "LG Bridge", bu I don't have Windows and haven't yet tried in virtualbox.
Is there any way to unbrick the device? Please help an idiot!
Sorry, you have to find a Windows box I'm afraid, LG is only offering Windows software for flashing. But chances are quite good that you are able to revive the telephone that way. I have bricked my phone as well but was able to unbrick it this way:
Go to www.lg.com, choose your language, select download, software and firmware.
Select smartphone, Android smartphones, K-series and your model number. This is only to come to the download site of LG Bridge, I guess it's not really important to choose the precise model!
Download LG Bridge, install and start it.
Let it update itself and the USB drivers and keep the software running.
Switch off the phone, press Volume up and keep holding that button.
Connect the phone with via USB with the PC while still pressing Volume Up. The phone should be recognized by the PC (install USB driver) and by LG Bridge (watch the status line to the left, it should show the phone type and USB)
The phone should automatically switch on and show a download screen (yippee!)
Select the second tab "software update" and then click on "correct update error" in the lower right. It should automatically download the correct firmware from the internet, so this is rather fool proof!
Click through it and this should start the flashing process, at the end the phone will automatically reboot, ask for the PIN, etc.
Unbricked!!!
Above instruction worked for me on a completely demolished phone. Lineage OS, changed FS, root attempted, I almost though that's it, but no, it recovered, thumbs up.
I haven't tried in Virtual Box, so I cannot tell if this is working. But you've got nothing to loose, right, so why not try it?
xor512 said:
I was trying to flash lg-k350n with LineageOs and make a whole bunch of idiotic deeds, so currently I'm felling like dying is the best option for me.
1. I've used this tutorial: .getdroidtips.com/install-custom-rom-using-twrp-recovery. It clearly says that this ROM is for Android 8.0 Oreo, while mine is Android 6.0 Marshmallow. Nevertheless I've downloaded ROM lineage-15.0-20170913-Unofficial-MT6735-64-bit.zip. For some reason TWRP mentioned here getdroidtips.com/lineage-os-15-lg-k8-8-0-oreo/ did not wok for me but I've googled a bit and found something called TWRP-recovery-for-LG-K8.img which worked (not by fastboot flash TWRP-recovery-for-LG-K8.img since this TWRP appeared to be to big but simply by fastboot boot TWRP-recovery-for-LG-K8.img).
So I just did:i
turn on debugger
turn off oem lock
adb boot bootloader
fastboot boot TWRP-recovery-for-LG-K8.img
Feeling happy that TWRP loaded nicely I had not done any backjup and just wiped system as suggested here: lineageos.org/devices/h990/install. Then I've tried to installl the Android 8..0. ROM with obviously did not work. And I've got left with a TWRP working and then I've put the last needle in my coffin - I've rebooted hoping that some hard reset or recovery will fix things for me.
So now I have a phone which I'm able to put to recovery, but it does not recover anything. The phone just go dead after such a recovery.
I cannot put it into fastboot mode, if I could, I would just run 'fastboot boot TWRP-recovery-for-LG-K8.img' and at least had a chance to google a bit for maybe a vanilla ROM or anything working, which I could've later installer.
I've seen that there is a way to put the phone into download mode when it will download stuff from S/W "LG Bridge", bu I don't have Windows and haven't yet tried in virtualbox.
Is there any way to unbrick the device? Please help an idiot!
Click to expand...
Click to collapse
same here, we are two now.
Don Pedro! said:
Sorry, you have to find a Windows box I'm afraid, LG is only offering Windows software for flashing. But chances are quite good that you are able to revive the telephone that way. I have bricked my phone as well but was able to unbrick it this way:
Go to www.lg.com, choose your language, select download, software and firmware.
Select smartphone, Android smartphones, K-series and your model number. This is only to come to the download site of LG Bridge, I guess it's not really important to choose the precise model!
Download LG Bridge, install and start it.
Let it update itself and the USB drivers and keep the software running.
Switch off the phone, press Volume up and keep holding that button.
Connect the phone with via USB with the PC while still pressing Volume Up. The phone should be recognized by the PC (install USB driver) and by LG Bridge (watch the status line to the left, it should show the phone type and USB)
The phone should automatically switch on and show a download screen (yippee!)
Select the second tab "software update" and then click on "correct update error" in the lower right. It should automatically download the correct firmware from the internet, so this is rather fool proof!
Click through it and this should start the flashing process, at the end the phone will automatically reboot, ask for the PIN, etc.
Unbricked!!!
Above instruction worked for me on a completely demolished phone. Lineage OS, changed FS, root attempted, I almost though that's it, but no, it recovered, thumbs up.
I haven't tried in Virtual Box, so I cannot tell if this is working. But you've got nothing to loose, right, so why not try it?
Click to expand...
Click to collapse
your phone cannot be trusted loooooop, cannot goto download and fastboot mode...
If you don't manage to enter download mode you have probably indeed bricked the phone. If what I've written above doesn't work for you I know of no other way to resurrect it, sorry.
This is because you cannot burn TWRP to the Flash plus there's no tool available to bootstrap an LG phone with a completely naked or corrupted Flash. There must be something like that, because a freshly manufactured phone has by definition a naked Flash.
With Samsung phones you have Odin and with it it is possible to burn a software to a completely dead phone. So it is almost impossible to hard brick it. With LG unfortunately it is different. Plus this phone is somehow crippled, it has only a very, very limited amount of Flash. So I would recommend to not care for this phone anymore, it's not worth it, and instead get a current one with a decent amount of memory.
my oneplus nord n10 5g is stucked on fastboot. to reinstall stock rom , i want to unlock bootloader , but my usb debudding and oem unlocking is off. how can i fix that ?
hfsva007 said:
my oneplus nord n10 5g is stucked on fastboot. to reinstall stock rom , i want to unlock bootloader , but my usb debudding and oem unlocking is off. how can i fix that ?
Click to expand...
Click to collapse
You don't need either adb debugging or OEM unlock ticked to reset it to stock.
Just go into edl mode on your phone and start the process.
ninjasinabag said:
You don't need either adb debugging or OEM unlock ticked to reset it to stock.
Just go into edl mode on your phone and start the process.
Click to expand...
Click to collapse
Thanks mahn thatks for the help. the first time im head about edl mode. download the edl mode firmware and flashed it. its worked......thank a lotb
hfsva007 said:
Thanks mahn thatks for the help. the first time im head about edl mode. download the edl mode firmware and flashed it. its worked......thank a lotb
Click to expand...
Click to collapse
Care to explain how to do it please?
I get into fastboot, but I cant get in to EDL mode in any way.
There are a few other posts in this forum on this subject. I almost want to ask mods for a sticky on it, as it seems to screw up a lot of people. The threads are all there, I won't repeat them here, but here's the stuff I didn't find obvious:
Make sure you have the right drivers installed. There is a SPECIAL set of Qualcomm drivers- different from the phone, and anything fastboot/ADB, needed to make Windows happy. Without this, you will get nowhere.
If Windows isn't your OS, and you are running an emulator (e.g. VirtualBox on Linux), make sure the USB ports are pass-through to the VM. This often requires permissions settings NOT DONE by the installer.
Likewise, make sure you pull your computer off the internet during this process or Windows may randomly reboot you to do system updates, with your phone half-flashed.
When you use the plug-in method for EDL, YOU ONLY GET IT FOR LIKE 3-5 SECONDS. You will not have a screen indication. You will not have vibration, or any other signal I know of beyond the USB device indication.
Quick process refresher: If memory serves (it has been a while) have the phone powered off, hold AND CONTINUE TO HOLD both volume buttons, and plug the phone in. *THEN* it should show up in Windows as a Qualcomm device. Let go of the buttons, take a deep breath, pat yourself on the back for having VM and drivers installed correctly. Get the phone powered off again however you can, then repeat the process again with the flash tool running, and it should give you a short window of "ready" or whatever for you to start the flash. Once you do that, and it goes into "beginning firehose" something or other, you can let go of the volume buttons. If you miss the window, repeat again until you hit it.
FWIW, it is pretty much impossible to brick a OnePlus without physical damage. The EDL mode is a separate methodology that allows a complete overwrite of everything that can be overwritten.