I have LineageOS 16.0
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Now I can't boot to OS because it boots straight to recovery.
The solution is to flash normal recovery and flash LineageOS zip.
But I can't transfer Recovery.img to my OnePlus One.
While I'm in Recovery, ADB is not working and there's no option to enable it.
And while I'm in Fastboot, PC can't see any fastboot devices.
It's not the PC's fault because it can recognize my Xiaomi Redmi Note 7 in both ADB and Fastboot mode.
So basically I need a way to transfer Recovery.img from PC to OnePlus One.
I can access only TWRP and Fastboot.
I can't do anything over USB cable.
OnePlus One doesn't have microSD card slot so I can't do it that way.
And I tried plugging in USB OTG drive and it phone can't recognize it. It won't even send the power to OTG drive.
eldin90 said:
And I tried plugging in USB OTG drive and it phone can't recognize it. It won't even send the power to OTG drive.
Click to expand...
Click to collapse
Use a low current flash drive, e.g. Transcend JetFlash 380 32 GB USB 2.0 OTG [200mA].
ze7zez said:
Use a low current flash drive, e.g. Transcend JetFlash 380 32 GB USB 2.0 OTG [200mA].
Click to expand...
Click to collapse
I don't think that'll work.
Phone doesn't give power to USB devices at all.
I tried plugging in multiple devices that used to work before (2 different USB thumb drives, both directly via micro USB port and via micro USB to USB 2.0 adapter, tried plugging in another phone, mouse, gamepad, micro USB to Ethernet adapter)
All those stuff used to work before while phone was on. But now they don't get power at all.
I don't know could it be because of Recovery?
I haven't tried plugging in OTG devices while in Recovery before.
eldin90 said:
While I'm in Recovery, ADB is not working and there's no option to enable it.
And while I'm in Fastboot, PC can't see any fastboot devices.
Click to expand...
Click to collapse
After entering:
Code:
adb devices
what you see in recovery mode?
---edit---
Use the USB 2.0 port on your PC.
ze7zez said:
After entering:
Code:
adb devices
what you see in recovery mode?
---edit---
Use the USB 2.0 port on your PC.
Click to expand...
Click to collapse
I don't see anything when I enter adb devices.
When I use any other phone I can see it after entering adb devices. But when I use OnePlus One I can't see anything.
And I only have USB 2.0 ports on my PC.
eldin90 said:
I have LineageOS 16.0
I used MutiROM before, uninstalled it, but MultiROM Recovery is still installed.
Today I downloaded update for LineageOS but I got "Updater process ended with ERROR: 7"
Click to expand...
Click to collapse
Are you sure you have an unmounted system partition before installing the ROM?
This message is the result of a mismatch between the build.prop entry from ROM and the TWRP installer script.
ze7zez said:
Are you sure you have an unmounted system partition before installing the ROM?
This message is the result of a mismatch between the build.prop entry from ROM and the TWRP installer script.
Click to expand...
Click to collapse
System partition is unmounted.
MultiROM TWRP gives me that error only when flashing some ROMs.
And it gives it to those ROMs always, no matter what I do.
Problem is that I only have LineageOS 16.0 zip on the phone and I don't have any other recoveries besides that MultiROM recovery.
Is there any way to boot the OS?
It worked fine before I tried to update it and it looks like all system files are still there.
I guess that failed update shouldn't had deleted any system files because it failed before it started doing anything.
I don't know what's making phone boot directly into recovery.
It won't even try to boot OS.
It goes straight into recovery every time.
eldin90 said:
System partition is unmounted.
MultiROM TWRP gives me that error only when flashing some ROMs.
And it gives it to those ROMs always, no matter what I do.
Problem is that I only have LineageOS 16.0 zip on the phone and I don't have any other recoveries besides that MultiROM recovery.
Is there any way to boot the OS?
It worked fine before I tried to update it and it looks like all system files are still there.
I guess that failed update shouldn't had deleted any system files because it failed before it started doing anything.
I don't know what's making phone boot directly into recovery.
It won't even try to boot OS.
It goes straight into recovery every time.
Click to expand...
Click to collapse
There should always be an original ROM for installation and several recovery versions in the phone's memory.
Now you have the use of restoring rom.
Clear the cache. First, try to recover only the Boot, and if that doesn't help, the entire backup.
You also have a powerful tool in TWRP in the form of a terminal and busybox commands, so act.
ze7zez said:
There should always be an original ROM for installation and several recovery versions in the phone's memory.
Now you have the use of restoring rom.
Clear the cache. First, try to recover only the Boot, and if that doesn't help, the entire backup.
You also have a powerful tool in TWRP in the form of a terminal and busybox commands, so act.
Click to expand...
Click to collapse
I tried wiping Cache and Dalvik / ART Cache
Still boots directly to recovery.
I don't have any backups or recovery installations on phone's memory.
I only have backup from 2 months ago that contains only boot and cache.
I restored it but it still boots directly to recovery.
What terminal commands should I use to fix this?
eldin90 said:
I tried wiping Cache and Dalvik / ART Cache
Still boots directly to recovery.
I don't have any backups or recovery installations on phone's memory.
I only have backup from 2 months ago that contains only boot and cache.
I restored it but it still boots directly to recovery.
What terminal commands should I use to fix this?
Click to expand...
Click to collapse
Since you don't maintain software hygiene, it's probably no better with hardware.
Clean the USB socket without damaging the connection. Clean the Vol- key in several ways.
Check if Odin can see the connection.
I have nothing more to add.
ze7zez said:
Since you don't maintain software hygiene, it's probably no better with hardware.
Clean the USB socket without damaging the connection. Clean the Vol- key in several ways.
Check if Odin can see the connection.
I have nothing more to add.
Click to expand...
Click to collapse
I work at coal coke industry and this happened about a month ago.
While I was charging the phone, coke dust inside the phone started burning and melted charger and USB socket together.
Guy from repair shop opened the phone and replaced USB socket with another one.
Is it possible that he didn't connected it correctly to the motherboard?
Or USB socket that he put wasn't exactly the same as the one that was originally there?
After he fixed it, we only tested can it charge the phone.
I haven't tried connecting phone to PC since then.
Anyways, is it possible to do something with terminal?
There has to be a file or something that's telling the phone to boot straight into recovery, right?
Can I remove or modify that file if it exists so phone boots into OS instead of recovery?
Vol- button isn't the problem.
It worked fine until I tried to update the OS.
And I can boot to Fastboot by holding Power and Vol+ buttons.
eldin90 said:
I work at coal coke industry and this happened about a month ago.
While I was charging the phone, coke dust inside the phone started burning and melted charger and USB socket together.
Guy from repair shop opened the phone and replaced USB socket with another one.
Is it possible that he didn't connected it correctly to the motherboard?
Or USB socket that he put wasn't exactly the same as the one that was originally there?
After he fixed it, we only tested can it charge the phone.
I haven't tried connecting phone to PC since then.
Anyways, is it possible to do something with terminal?
There has to be a file or something that's telling the phone to boot straight into recovery, right?
Can I remove or modify that file if it exists so phone boots into OS instead of recovery?
Vol- button isn't the problem.
It worked fine until I tried to update the OS.
And I can boot to Fastboot by holding Power and Vol+ buttons.
Click to expand...
Click to collapse
Using md5sum check the phone ROM.zip of your Lineage you tried to install. Then check the ROM.zip checksum on the server and compare the checksums. You will learn about the quality of the file.
If someone undertook to replace the usb socket, it is obvious that you should check not only the charging lines, but also the data transmission line.
From that I would repair the OPO.
ze7zez said:
Using md5sum check the phone ROM.zip of your Lineage you tried to install. Then check the ROM.zip checksum on the server and compare the checksums. You will learn about the quality of the file.
If someone undertook to replace the usb socket, it is obvious that you should check not only the charging lines, but also the data transmission line.
From that I would repair the OPO.
Click to expand...
Click to collapse
I did sha256 checksum and it's exactly the same as on the server
https://mirrorbits.lineageos.org/fu...16.0-20191118-nightly-bacon-signed.zip?sha256
Mount System partition
Code:
mount /system
and show:
Code:
grep twrp /tmp/recovery.log
Code:
ls -l /data/media/
Code:
ls -l /data/media/0/
Code:
grep lineage /system/build.prop
Code:
cd /
find . -name recovery*
find . -name *.zip
find . -name *.img
It's not everything. When you're finished we'll go on.
ze7zez said:
Mount System partition
Code:
mount /system
Click to expand...
Click to collapse
I did that
ze7zez said:
and show:
Code:
grep twrp /tmp/recovery.log
Click to expand...
Click to collapse
imageupload
ze7zez said:
Code:
ls -l /data/media/0/
Click to expand...
Click to collapse
This one only shows files and folders from internal memory. Nothing important there
ze7zez said:
Code:
ls -l /data/media/
Code:
grep lineage /system/build.prop
Click to expand...
Click to collapse
ze7zez said:
Code:
cd /
find . -name recovery*
find . -name *.zip
find . -name *.img
It's not everything. When you're finished we'll go on.
Click to expand...
Click to collapse
1. Change /sdcard/recovery.log to a unique name.
2. Make Advanced -> Copy Log (Include Kernel Log)
3. Change /sdcard/recovery.log to a unique name.
4. Make a full backup ROM if you haven't already done so.
5. Wipe -> Advanced Wipe: Dalvik, System, Data, Cache
6. Install lineage without "Reboot after installation is complete".
7. Show messages from the installation terminal.
8. Make Advanced -> Copy Log (Include Kernel Log)
9. Change /sdcard/recovery.log to a unique name.
10. Reboot -> System
??
I did all steps.
After wiping everything and trying to install LineageOS zip I get this (same as before)
When I tried to reboot, TWRP warned me that there are no OS installed. Phone still boots straight to recovery.
eldin90 said:
I did all steps.
After wiping everything and trying to install LineageOS zip I get this (same as before)
When I tried to reboot, TWRP warned me that there are no OS installed. Phone still boots straight to recovery.
Click to expand...
Click to collapse
You have twrp installed for Oneplus 3 (E3004) and you want to upload a ROM for Oneplus One.
ze7zez said:
You have twrp installed for Oneplus 3 (E3004) and you want to upload a ROM for Oneplus One.
Click to expand...
Click to collapse
I have installed TWRP that I downloaded from here
https://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738/amp
It's says it's for OnePlus One.
And I used to flash Ubuntu Touch and some older Resurrection Remix and CyanogenMod ROMs with it.
eldin90 said:
I have installed TWRP that I downloaded from here
https://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738/amp
Click to expand...
Click to collapse
This is impossible because your TWRP is release 3.1.1-0, which was created after 2017-05-17, which is much later than TWRP from the page you provided.
Show:
Code:
grep fingerprint /sdcard/recovery.log
Related
Hi,
I have my TF700 unlocked for a while with good results, but yesterday it was a little bit slow and i did a wipe on the bootloader thinking that it was a good idea... i did not read what dangerous it is....
After, it freezes on the asus logo on the boot.
I tried to go to the recovery and freezes on the teamwin screen....but after like 40 minutes doing nothing it goes into the TWRP 2.5.
I can go to all the options inside but says that internal memory has 0MB, that /data /system is unmount, if I try to mount freezes.
Last time (one more time waiting 40minutes) I tried to reinstall CROMIx 4.7 from the external sdcard using the install option of TWRP. I did it with no issues until the end, but it didn't finishied i think because it was on the same again.
It happened to anyone, about this 40minutes to go to recovery ?
Any solution / idea ?
the best for all.
António
antonio3073 said:
I tried to go to the recovery and freezes on the teamwin screen....but after like 40 minutes doing nothing it goes into the TWRP 2.5.
I can go to all the options inside but says that internal memory has 0MB, that /data /system is unmount, if I try to mount freezes.
Click to expand...
Click to collapse
Connect via adb shell to your recovery and post the output of
Code:
cat /proc/partitions
hexdump -C -n 512 /dev/block/mmcblk0p3
_that said:
Connect via adb shell to your recovery and post the output of
Code:
cat /proc/partitions
hexdump -C -n 512 /dev/block/mmcblk0p3
Click to expand...
Click to collapse
First, thanks a lot
I have adb installed and working, but no connection to TF by USB. I didn't know why because it worked without problems, but now on my PC says that is a driver problem.
I did the same on terminal inside TWRP at TF, that's i think the only way to interact with TF.
i am just waiting more 20minutes.... to go into TRWP to put here the result
antonio3073 said:
I have adb installing and working, but no connection to TF by USB. I didn't know why because it worked without problems, but now on my PC says that is a driver problem
Click to expand...
Click to collapse
Then you need to fix your driver problem first. The recovery reports itself as a different USB device than the regular Android OS (at least the serial number is different), that may confuse your driver.
I can't help you with your driver issues though (Linux doesn't need drivers for adb).
_that said:
Then you need to fix your driver problem first. The recovery reports itself as a different USB device than the regular Android OS (at least the serial number is different), that may confuse your driver.
I can't help you with your driver issues though (Linux doesn't need drivers for adb).
Click to expand...
Click to collapse
Please see the result here
View attachment 2244302
View attachment 2244303
better pictureView attachment 2244309
antonio3073 said:
Please see the result here
Click to expand...
Click to collapse
Partition sizes look OK (but very blurry ), so your recovery can access the eMMC. This is good, because it means you should be able to repair your system.
The output of the hexdump command would be interesting - no idea why it doesn't work for you.
Edit: "I/O error" on the new screenshot looks worrying, also "unable to set emmc bootloader message".
More detailed error messages should be available as the output of the "dmesg" command, but this will be very long, so you'll need adb for this (command: "adb shell dmesg > output.txt").
_that said:
Partition sizes look OK (but very blurry ), so your recovery can access the eMMC. This is good, because it means you should be able to repair your system.
The output of the hexdump command would be interesting - no idea why it doesn't work for you.
Click to expand...
Click to collapse
The last picture is better and has the result of the hexdump
I tried to take out output.txt of the tablet by external sdcard but recovery file manager did not save the file on external.
Than i have to ways:
1- windows usb driver solution. do you know any driver for it ?
2- I have a computer with a version of linux. Where can i learn how to install adb on it ?
Is it not possible to reinstall all from begining starting the bootloader by external sd, because the recovery seems to install ?
antonio3073 said:
I tried to take out output.txt of the tablet by external sdcard but recovery file manager did not save the file on external.
Than i have to ways:
1- windows usb driver solution. do you know any driver for it ?
2- I have a computer with a version of linux. Where can i learn how to install adb on it ?
Is it not possible to reinstall all from begining starting the bootloader by external sd, because the recovery seems to install ?
Click to expand...
Click to collapse
For linux you don't need drivers, just install the AndroidSDK for linux, there are lots of guides wich can help you do it, just search on google or xda.
You can try to install a rom from external memory but imo it will also fail.
Pretoriano80 said:
For linux you don't need drivers, just install the AndroidSDK for linux, there are lots of guides wich can help you do it, just search on google or xda.
You can try to install a rom from external memory but imo it will also fail.
Click to expand...
Click to collapse
Hi, coming again after a while to discover that my daughter's computer has linux. I am starting to be a entusiastic of it...in fact i am on it!!!.
Now i can use adb without problems and i got output.txt
Please I apreciate your suport for the next step.
View attachment output.txt
thanks a lot
<3>[ 8078.194240] mmcblk0: error -110 transferring data, sector 2532352, nr 32, cmd response 0x2000900, card status 0x0
Click to expand...
Click to collapse
Error -110 is timeout, meaning the eMMC did not react in time on the kernel's commands.
I've seen this error at recovery startup when the recovery is incompatible with the bootloader, and I've seen it for external microSD cards because the TF700 has stability problems with the UHS-1 protocol.
Try restarting the tablet (to recovery, because it will do that anyway) and get another dmesg output within the first minute - maybe there are interesting messages in the startup sequence.
_that said:
Error -110 is timeout, meaning the eMMC did not react in time on the kernel's commands.
I've seen this error at recovery startup when the recovery is incompatible with the bootloader, and I've seen it for external microSD cards because the TF700 has stability problems with the UHS-1 protocol.
Try restarting the tablet (to recovery, because it will do that anyway) and get another dmesg output within the first minute - maybe there are interesting messages in the startup sequence.
Click to expand...
Click to collapse
a dmesg after 40minutes of booting to recovery
View attachment output.txt
there is anyway to reinstall bootloader from adb?
antonio3073 said:
a dmesg after 40minutes of booting to recovery
View attachment 2248488
Click to expand...
Click to collapse
You could not get an adb connection any earlier?
_that said:
You could not get an adb connection any earlier?
Click to expand...
Click to collapse
i rebooted, and yes, i have adb just after appear teamwin screen for the next 40minutes
new output
antonio3073 said:
i rebooted, and yes, i have adb just after appear teamwin screen for the next 40minutes
new output
Click to expand...
Click to collapse
OK, the timeouts start almost immediately after the startup, but the recovery kernel does detect the correct partitions. So maybe it just can't write properly but read...
Let's try a "defibrillation":
Download this zip file to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
* Unpack it - you'll get a file named "bootit.ko".
* Push it to your tablet, e.g. with "adb push bootit.ko /".
* Run "adb shell insmod /bootit.ko"
This should reboot immediately to the bootloader menu where you can try to cold-boot Android, or to enter the recovery the "normal" way, or you can try to use fastboot to reinstall a recovery. I would not try to flash the bootloader until it is confirmed your eMMC works properly at least outside the recovery.
Edit: for reference, this is the thread where I developed the "bootit.ko" module to unbrick a TF700: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
OK, the timeouts start almost immediately after the startup, but the recovery kernel does detect the correct partitions. So maybe it just can't write properly but read...
Let's try a "defibrillation":
Download this zip file to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
* Unpack it - you'll get a file named "bootit.ko".
* Push it to your tablet, e.g. with "adb push bootit.ko /".
* Run "adb shell insmod /bootit.ko"
This should reboot immediately to the bootloader menu where you can try to cold-boot Android, or to enter the recovery the "normal" way, or you can try to use fastboot to reinstall a recovery. I would not try to flash the bootloader until it is confirmed your eMMC works properly at least outside the recovery.
Edit: for reference, this is the thread where I developed the "bootit.ko" module to unbrick a TF700: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
it does a shutdown imediate, not a reboot
i have to turn on again, but happen the same
I was looking at output file trying to undestand something. I saw fist error is
lost page write due to I/O error on mmcblk0p8
do you think is a hardware problem on the internal sdcard and nothing to do?
I tried to put a new recovery twrp 2.6 by adb but:
~ # dd if=/twrp.blob of=/dev/block/mmcblk0p4
dd: writing '/dev/block/mmcblk0p4': I/O error
1+0 records in
0+0 records out
0 bytes (0B) copied, 16.133516 seconds, 0B/s
The I/O error is everywhere .....?
antonio3073 said:
do you think is a hardware problem on the internal sdcard and nothing to
do?
Click to expand...
Click to collapse
Hard to say... at least the recovery has severe problems writing to the eMMC - which is strange, because normally it should be compatible with the recent bootloaders. Since you can't boot anything else we don't know if it's only the recovery or a hardware problem. Also strange that my reboot-to-bootloader module just shuts down in your case instead of rebooting.
I'm out of ideas.
If you don't have ideas, imagine myself....
This case for me is a return to my old times on electronics and systems at the time programing assembler on microprocessors intel and texas...good times..
Now more than a destroied tablet (there is a lot more on shops to buy) it's a chanlange for me to understand how android is structured and how it process.ware
Is true that there is 3 parts?:
- bootloader (like bios on PC)
- recovery (like software to change bios on PC)
- firmware (like windows on PC)
all are in diferent mount files, correct ?
In this case the bootloader works normal since power+vol-, can i conclude that bootloader is ok? is function is to stop there?
The recovery that is 40minutes to appear seems to be bad, correct? than i tried to reinstall.
The firmware that no more appear problebly it is not invoked because it stops before.?
It seems that are some problems wirting on internal sdcard as we see on output.
The strange is if i try to reinstall firmware cromix, it goes to the end wiithout any problem, just doesnt start, what seems to doesn't have problems to write..
On the recovery on file manager or on the install says internal space 0MB, not strange ?
can we make something diferent even has risk?
I flashed eos-tf101-20130704-121, and it does not boot. I've tried several times, and I made sure to wipe the system, cache, etc. why is it not working?
also, how do I get into download mode?
That's an ancient build of a dead ROM project
KatKiss is the new EOS
http://forum.xda-developers.com/showthread.php?t=2362764
Unfortunately, I don't have a spare sd card, and I can't seem to get download mode to work, so I was hoping I could install the ROM update, and install KatKiss. I am working on getting KatKiss though!
If yo boot to recovery you can use ADB to push files to your tablets internal memory to flash.
frederuco said:
If yo boot to recovery you can use ADB to push files to your tablets internal memory to flash.
Click to expand...
Click to collapse
sorry - how do I do this? never used adb before.
sniper8752 said:
I flashed eos-tf101-20130704-121, and it does not boot. I've tried several times, and I made sure to wipe the system, cache, etc. why is it not working?
also, how do I get into download mode?
Click to expand...
Click to collapse
you have to wipe cache and dalvik after flashing the rom
KronicSkillz said:
you have to wipe cache and dalvik after flashing the rom
Click to expand...
Click to collapse
no luck.
Im going to guess that you have CWM Recovery installed ?
If yes, that is likely the reason for it not booting
You'll need to put the TF into APX Mode (Volume up & Power while connected to the PC > USB)
Nothing will appear on the TF screen, but the PC should recognise it
Follow the instructions here to get TWRP Recovery installed instead
http://forum.xda-developers.com/showthread.php?t=1688012
sniper8752 said:
sorry - how do I do this? never used adb before.
Click to expand...
Click to collapse
You need adb from the Android SDK. I have a zip of the files you need here: http://db.tt/b9dQ6xzp
Unzip these to c:\adb\
Plug your tablet in using the USB cable. Your computer should detect a new device. Update the driver with the Naked Drivers 0.72 ADB driver found in the Dev forum (I think it is on page 2 of threads). If you are running Win 8, there are some extra steps to allow you to use this driver.
Once your devices shows in the device manager as an ADB device, open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
At this point, it will probably restart the daemon and then it should show a recovery device. If it does, you can proceed. If not, check that your cable is good, and that an ADB device is showing in the device manager.
Grab the ROM of choice and any GAPPS and kernel that you want to move over to your device. Put them in the c:\adb folder. They will be referred to a ROM.zip, GAPPS.zip and kernel.zip going forward.
Execute the following:
Code:
adb push ROM.zip /sdcard/
adb push GAPPS.zip /sdcard/
adb push kernel.zip /sdcard/
Note there is a space between the zip and the /sdcard/. If you omit this space it will not work.
After each time the "adb push" is executed, it may take up to 10 minutes to push the file depending on how big it is. Just be patient until it says it was pushed successfully.
Once this is done, you should see these files in the internal memory of your device when in recovery.
thanks! got it to work.
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
djakolis said:
Hello people,
First of all, I'm not an expert so pardon on that.
I had a MicroSD card in my tablet and it was partitioned using GParted, 2 partitons - fat32 and ext4. I erased the whole tablet with Wipe option in TWRP and installed move2sd.zip.
Anyway... When I pressed Reboot to recovery, tablet restared, showed TWRP and screen went on and off showing TWRP logo, like it was trying to load TWRP. Now... Since I installed that .zip file it might have written some code to use MicroSD card as boot? I reinstalled TWRP by flashing it via fastboot and was able to enter TWRP again.
Now the stupid part... Since it read 0mb on internal card (tablet), I wanted to fix it by formating Data... It didnt do the trick cause /data and other folders couldn't have been found. That's where I restarted the tablet and pressed Wipe data on the screen with 3 icons (RCK, Android, Wipe data)... Since then I only see 2 screens - bootup screen with Asus logo and message: Device is unlock and the next screen is TWRP and it flickers again, goes on and off just as if it was trying to load TWRP.
I cannot reflash recovery cause there is no fastboot?
I just hope this is not an expensive paper...
Click to expand...
Click to collapse
You can still enter RCK ??
Not that this helps your situation, so apologies.
Just started getting the screen flicker/lines randomly when handeling it. So my guess was just the loosining of something internally.
I`m also freecarding it. So that hadden`t crossed my mind.
Time for a tear down vid I guess.
Best of luck tho.
I'll make a quick video. Be right back to you...
Edit: I cannot post a video due to XDA rules, but you can search for it: TF700 no fastboot, recovery stuck (search for recent uploads, d jakolis is my username on YouTube) If you guys cannot find it, I can email the link to you.
As you can see in the video, there is not much left to do with the tablet.
However, when I selected Wipe Data on bootloader, did it wipe kernel too? I'm asking this cause I had installed data2sd.zip along with its corresponding kernel.
What would happen if someone else with the same device installed the custom ROM on MicroSD card and handed me his MicroSD card to pop in my tablet? Would it boot off it? Would I be able to enter Android and maybe somehow re-flash recovery and stock kernel along with stock ROM?
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
_that said:
You should still be able to connect via adb. Try adb pull /tmp/recovery.log and adb logcat.
Click to expand...
Click to collapse
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
djakolis said:
Tried adb pull /tmp/recovery.log and got recovery.txt file.
Adb logcat showed this: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
Looks like your /data partition is not formatted properly. Try this (don't type "#" and the following comment):
Code:
adb shell # connect to a shell on the device
killall -19 recovery # suspend the recovery so that it doesn't interfere with formatting
make_ext4fs /dev/block/mmcblk0p8 # format /data
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 # remove "wipe data" request
reboot
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
djakolis said:
Wow... I don't know what to say. I'm looking at the fastboot screen! :highfive:
I didn't type the last line of your code because it rebooted itself after format data was complete - make_ext4fs... Is there any consequence for not typing the last line?
Click to expand...
Click to collapse
Maybe the "killall -19" stuff didn't work and the recovery was not suspended, so it may have somehow determined that the wipe was finished and initiated a reboot.
djakolis said:
Alright, I'm in recovery right now. Question: What is installed on the tablet right now? If anything... May I proceed with installing stock ROM and maybe do nvflash process to have an unbrickable device?
Click to expand...
Click to collapse
What is installed? Whatever recovery, kernel and ROM you installed last. No other apps since you just formatted /data.
Since the nvflash (flatline) process saves only BCT, bootloader, partition table and unlock token (basically all the stuff you need to get fastboot working on a hard bricked tablet), you can do that now.
djakolis said:
P.S. What does it take to learn all these things? I'm curious cause I like coding, so if you feel happy to share it, I'm all ears.
Click to expand...
Click to collapse
Lots of reading here, lots of googling and more reading. Experience with Linux on PCs helps too.
where can i wirte this codes i dont know , can anyone help me??? i have same problem
i can not connect device also in adb mode pc didnt accept the drivers
y3akup said:
i can not connect device also in adb mode pc didnt accept the drivers
Click to expand...
Click to collapse
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
berndblb said:
If you can still enter recovery (which one do you have?) you can use the build in Terminal.
Otherwise you have to get the adb drivers installed and working. There is no other way if you do not have a working recover and cannot get into fastboot.
Try this tool: http://forum.xda-developers.com/showthread.php?t=2588979
Once you get the drivers installed boot the tablet to recovery and post what you get with this command:
Code:
adb devices
Click to expand...
Click to collapse
i tried this tool before but still in the device manager page i have transformer device with yellow flag
y3akup said:
i tried this tool before but still in the device manager page i have transformer device with yellow flag
Click to expand...
Click to collapse
You need to install the drivers - right click on the yellow ? and choose install drivers
Use these ones here:
http://www.androidfilehost.com/?fid=23329332407571009
http://www.androidfilehost.com/?fid=2332933240
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
y3akup said:
now i have
0123456789ABCDEF recovery
but commands that from other posts didnt work
Click to expand...
Click to collapse
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
sorry but it says dd is not inside or outsite command and bla bla i cant translate directly but like this
is not recognized as an internal or external command, operable program or batch file
berndblb said:
Try this command only:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
Copy and paste it into your cmd window
Click to expand...
Click to collapse
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
y3akup said:
now i could enter the recovery and nearly ten times i installed rom but still it couldnt open twrp and bootloader numbers i checked but i think i did something wrong what can i do now??
Click to expand...
Click to collapse
Splendid!
Now - did you a full wipe in TWRP before installing the rom? Select the Wipe option and swipe the button. Then re-install the rom.
On the last page of the Aroma installer you have the option of saving the installation log. Do it.
Then back to TWRP, go to Advanced and also save the recovery log.
If the ROM still doesn't boot, post both of those logs.
Also try to capture a logcat of the boot process
Code:
adb logcat -v long > logcat.txt
Post that one too.
Okay,
Basically when changing my OS from Paranoid android to Cyanogen mod 12 I messed up
I did a full data reset and factory reset on my phone wiping all the caches as well.
Unfortunately this deleted all my backups and my OS.
Now I have no OS to boot onto to and the only thing I can access is TWRP boot loader.
I need to find a way to move data from my computer to my phone so I can install the Cyanogen Mod ROM and GAPPS!!!
Please help!
BTW I know this was stupid as **** and the phone is effectively bricked at the moment.
:crying: :crying: :crying:
DizzyJarod said:
Okay,
Basically when changing my OS from Paranoid android to Cyanogen mod 12 I messed up
I did a full data reset and factory reset on my phone wiping all the caches as well.
Unfortunately this deleted all my backups and my OS.
Now I have no OS to boot onto to and the only thing I can access is TWRP boot loader.
I need to find a way to move data from my computer to my phone so I can install the Cyanogen Mod ROM and GAPPS!!!
Please help!
BTW I know this was stupid as **** and the phone is effectively bricked at the moment.
:crying: :crying: :crying:
Click to expand...
Click to collapse
Two options, reflash stock rom with fastboot or goto TWRP/Mount and select Enable MTP with usb plugged to pc.
Elessar76 said:
Two options, reflash stock rom with fastboot or goto TWRP/Mount and select Enable MTP with usb plugged to pc.
Click to expand...
Click to collapse
Cheers for the quick reply!
Where do I find Enable MTP in TWRP/Mount man?
All I can see is
Select Partitions to Mount:
[x] Data
[x] Cache
[ ] System
Storage: Internal Storage (12479 MB)
DizzyJarod said:
Cheers for the quick reply!
Where do I find Enable MTP in TWRP/Mount man?
All I can see is
Select Partitions to Mount:
[x] Data
[x] Cache
[ ] System
Storage: Internal Storage (12479 MB)
Click to expand...
Click to collapse
Is your TWRP updated? Mine is 2.8.1.0 and i have:
Data
Cache
System
USB OTG
And Enable MTP
Elessar76 said:
Is your TWRP updated? Mine is 2.8.1.0 and i have:
Data
Cache
System
USB OTG
And Enable MTP
Click to expand...
Click to collapse
No sorry man, mine is just 2.6.3.3 so it doesn't have those options.
Would adb be easier?
It's just getting my phone to be recognized by adb or windows that's troubling me.
DizzyJarod said:
No sorry man, mine is just 2.6.3.3 so it doesn't have those options.
Would adb be easier?
It's just getting my phone to be recognized by adb or windows that's troubling me.
Click to expand...
Click to collapse
Why don't update your TWRP? You can go to TWRP webpage and download new version for your model.
Adb sideload would be another option, yes.
Elessar76 said:
Why don't update your TWRP? You can go to TWRP webpage and download new version for your model.
Adb sideload would be another option, yes.
Click to expand...
Click to collapse
Thanks man but don't worry!
What I ended up doing is editing the drivers for my phone in windows to make them compatible with adb. Then with a adb command prompt open I wrote "push adb rom.zip /sdcard" to get the files on my phone. Finally I installed them with TWRP like usual!
Post the driver thing?
DizzyJarod said:
Thanks man but don't worry!
What I ended up doing is editing the drivers for my phone in windows to make them compatible with adb. Then with a adb command prompt open I wrote "push adb rom.zip /sdcard" to get the files on my phone. Finally I installed them with TWRP like usual!
Click to expand...
Click to collapse
How'd you do this? I'm at the same point you were at and I've got absolutely nothing, I'm devastated, need help ASAP
Hi, my G6-U10 is hard bricked and has gone to QDLoader 9008 mode so i cant go to recovery, fastboot,adb mode .
i need EMMC image of a similare device (G6-U10) so i can fix it following instructions in this thread .
i dont need whole EMMC image, just first 100-200 MB .
to extract EMMC, you need to be on stock rom with root access.
to do so:
1. Enable "USB debugging" in "Developer Options". then connect your device to Windows PC.
2. download and extract ADB. then run the following command through CMD:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/EMMC.img bs=100m count=1
note that you must enter each row separately and confirm the dialogs appeared on your device screen to grant root and adb access for pc. the option bs=100m mean that the dd command will only extract first 100MB of EMMC. and FYI, this file is only backup from system partition, not from any private files, no need to worry.
the extracted file will be in internal SD, named EMMC.img , compress it in ZIP or RAR so it will have much less size, then send it here to solve many people's problems. anybody does that, i'll appreciate.
Thanks for reading.
Credits and references:
@majdinj http://forum.xda-developers.com/showthread.php?t=2450045
@Jimmyz0r http://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
@tirta.agung http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://linoxide.com/linux-command/linux-dd-command-create-1gb-file/
http://unix.stackexchange.com/questions/134299/dd-bs-count-seek
https://yadi.sk/d/wtaBNFaUraZyg
washichi said:
https://yadi.sk/d/wtaBNFaUraZyg
Click to expand...
Click to collapse
Thanks bro, but it's just 100bytes, not 100Mbytes. i think you used bs=100 instead of bs=100m
please consider reuploading , you are my saviour
info on the progress:
I got EMMC image thanks to @washichi :good: (download it from attachments).
then i could finally wake my device up, in the fastboot and recovery, following instructions in this thread(first post).
i can go into Fastboot mode but though i had unlocked bootloader (before), but i can only flash recovery, system(partly) and boot partitions. other partitions give me error ((Remote: Not Allowed)).
the only recovery that i could go into, was the latest TWRP 3 . in recovery i can even connect my device in MTP mode to pc and see files on the internal SD! but i was not successful with flashing roms, it always gives me error mounting cache, system, data. ADB mode is also accessible, used adb sideload to flash rom, but it didnt worked too!
i think part of internal SD is damaged and need to be fixed somehow. still havent found out how.
so, for guys who are having problems similar to me or "Internal Storage Damaged blah blah" i recommend trying to follow these steps to see if their internal SD is still flashable or not:
1. Download an official Rom for your device and unpack it using HuaweiUpdateExtractor.
2. download and extract latest (at least 1.0.32) fastboot in the same folder as extracted huawei IMG files are (Gush bless me! there's too much grammatical erros in my texts )
3. connect your device in fastboot mode (instructions above).
4. go to the directory where all extracted files place. Hold shift and right click on empty space, chose "Open command window here".
Note: you must have an unlocked bootloader to be able to continue, type this command to see if its unlocked:
Code:
fastboot oem get-bootinfo
if you're unlocked, then continue reading, if not, i dont think there is a way to find unlock key for your device.even DC unlocker cant recognize your device in fastboot and adb.
5. now that you know you have an unlocked BL, type these commands one bye one:
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash tz tz.img
fastboot flash userdata userdata.img
fastboot flash [COLOR="RoyalBlue"]XXX [/COLOR][COLOR="SeaGreen"]XXX[/COLOR].img
as i said before, i could only flash 3 partitions with success. but if you where able to flash all parts with success, your extremely have a chance to revive your device. at last, type fastboot reboot to see if you boot up successfully, if not, you will go again in fastboot mode or recovery mode.
for me, default recovery mode just freezes, so i flashed TWRP 3 instead of default recovery. you can try that too.
one more thing: you might not be successful to reboot into recovery, you must restart until you succeed. if you stuck in freezed recovery, open the device back, unscrew the little steel plate (it has 2 screws) and dettach the battery cord, wait 3 secs, re-attach it. i have done it more than 300 times now i dont even know where is the steel plate
FYI, EMMC image in the attachment is for G6-U10 only and probably will not work for other G6 models. if you want G6-L11 emmc, i can share it for you.
if anything was not clear for you, ask me.
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Sashko98 said:
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Click to expand...
Click to collapse
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
bugggmenot said:
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
Click to expand...
Click to collapse
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Sashko98 said:
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Click to expand...
Click to collapse
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
bugggmenot said:
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
Click to expand...
Click to collapse
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Edit1: Tried to flash an update.zip which i made by using huawei tools extractor from the stock recovery but the verification aborted the update. Tried with CWM by using adb sideload but there was some error while sending, also tried with TWRP which seems to erase its memory everytime when i restart the phone, the adb sideload doesnt work and couldn't found the flashable zip after i pushed it in by using adb
Sashko98 said:
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Click to expand...
Click to collapse
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Sashko98 said:
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Click to expand...
Click to collapse
Greate! i dont know if they are similar or not but who cares, i'll give it a shot! please share files here i'll try and report back.
bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Why not try to repartition your device?
You can you the parted binary (google will find it) and put it on your /sdcard or / (the root folder). NOT your internald memory or any other partition thats your EMMC.
Now umount ALL partitions in recovery, except for the external sdcard. Go to the commandline in the recovery and cd to the parted binary. Now typ 'parted /dev/block/mmcblk0'.
Type 'print' to see your partition table.
You can now modify your partition table (only ext2 and fat32 partitions support, BUT you can format it whit your recovery soo it will be ext4. (Dont check RM format in settings!).
Hope this will fix the flashing problem.
Hard Brick
Hello guys, i don't know if this is the right place, but do you know how to unbrick Huawei Y550 - L03 from hard brick? My pc recognizes it in the device manager just as Android adapter PCUI (COM10) but the device itself doesn't show.
Thank you in advance if you can help me please. :crying:
Here i put EMMC for G6-L11 for people who need it:
Hello, can you explain how you made it from dead phone QDLoader 9008 to recovery?
bugggmenot said:
Here i put EMMC for G6-L11 for people who need it:
Click to expand...
Click to collapse
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
henrucci said:
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
Click to expand...
Click to collapse
only if your phone is G6-L11, then the answer is yes.
Win32disk killed for good all sdcards with g6-l11 image