Related
hey forum
as you can guess i'm bricked and don't have a file manager or terminal program on my phone.... fell like an idiot for even trying this rom now, any way of moving the mtd0.img and flash_image to /data without them?
regards scott
Code:
adb shell
mv path/to/file new/path/to/file
You may need chmod 755 if the file is meant to be executable, not sure though.
might sound stupid but how to i adb to phone i keep typing adb devices hoping it will pop-up but there is non... is there a mode i should be in?
USB debugging on, phone plugged into PC... The phone needs to be on too, either in recovery mode or normal usage. If you want to be writing stuff to /system you need to be in recovery mode. Be sure to mount /system too.
just went into recovery mode (power off>hold + back>bootloader>recovery (i belive thats recovery mode)) still no devices same with the phone turned on normal usage
another quastion if i could get my hand on nandroid files from someelses htc legend would it work on mine???
You need to be in clockworkmod recovery. Look into fake flash.
You can use someone else's nandroid, but you'll end up with all their data. Personal stuff too...
Sent from my GT-P1000
Fake flash is the best!
1. Just find the clockwork recovery ZIP file and put it in the root of your SD card as "update.zip" with small letters and without the quotes.
2. Power down your phone.
3. Hold Volume down and press Power.
4. Select Recovery and press Power again.
5. When you see the screen with the exclamation mark, hold Volume up and press Power.
6. From the menu screen select Install Update.zip from the SD card. Do not wory, the flash is not real. That's why it is called Fake flash.
7. Now you should be in the Clockwork Recovery.
Thx Guy I'm up and running going to keep clockwork and a ROM on my SD card all the time now
Sent from my Legend using XDA App
Ok, so rooted (razorclaw) ics 4.0.3 tf-101.
fully charged
when powering on, stalls at the eee pad screen. (sounds like a boot loop, but it doesn't go to recovery)
Cold boots fine, works great, no random reboots (yet)
Will not boot into recovery, has ww_epad-9.2.1.11-20120221 bootloader
stalls at "booting kernel image" I assume there is no recovery installed.. Tried to get cwm onto it but I cant get apx working, it wont recognize the device at all.
I didn't root it, someone else did and I have no idea what recovery is/was on it.
I bought the tablet used, and would like to fix it.
Once recovery is installed would this boot normally.
Ive been searching on here/transformer forums for a couple weeks and have thought I found the answer multiple times. I need a push in the right direction.
Tried to fix this for a while a couple months ago when ics first launched and gave up. (did the same thing when It had honeycomb on it)
edit::
the only solution I can come up with is using NVFLASH to try to restore it. Working on this right now, hopefully this is a sbk1//not working, cant seem to get the computer to recognize the device in apx mode. (win 7)
If your TF is rooted, you may want to give the RecoveryInstaller app a go.
http://forum.xda-developers.com/showthread.php?t=1346180&highlight=recovery
I forgot to add that I have tried that (tried it again just now.. twice, just incase it happened to work but it didnt.)
following these instructions:
"click the button and the Superuser app will ask for permissions. Then the tablet reboots and to enter it you have to keep the Volume - key pressed and when it the TF writes "Booting into recovery" on the screen press Volume + once"
also tried it without holding volume buttons when it reboots.
When I run it, and click the button to install recovery, it grants superuser permissions and then reboots, sticks at the eee pad screen again and it stalls at booting recovery kernal image. Anything Im missing?
Reflash a recovery image .sos and bootloader .ebt if the recovery image doesn't work.
Download any cwm flashable recovery and extract it twice to get the recovery blob out:
put the recoveryblob on your computer somewhere.
adb push C:\Location\Of\Blob\blob.blob /sdcard/
adb devices
adb shell
su
dd if=/sdcard/blob.blob of=/dev/block/mmcblk0p4 -
reboot
--
this should fix recovery.
Thanks for breaking that down! Im going to try this once I can get adb working.
Going to try another computer now. I'm beginning to wonder if the usb cord for my tf has gone bad.
You can do it on your tf too, via terminal emulator app since you can coldboot.
Download blob somewhere on tf, download term em. and run this part:
su
dd if=/Path/to/recoveryblob of=/dev/block/mmcblk0p4 -notice path/to is where you placed on Tf's INTERNAL storage.
reboot
Ok, went through it on the terminal emulator. Everything seemed to go ok, but on rebook, it still wont enter recovery (held the vol button of course) just hangs on "booting recovery kernal image"
Is BusyBox installed?
That it is, just reinstalled 1.20.. should i use a different version perhaps?
Ro.secure set to 0?
see the guide to flashing an insecure boot.img if it isn't, this may be the problem.
if you're on a rom this isn't the issue..
Try a different version of BB I suppose
simplywinter said:
Ok, went through it on the terminal emulator. Everything seemed to go ok, but on rebook, it still wont enter recovery (held the vol button of course) just hangs on "booting recovery kernal image"
Click to expand...
Click to collapse
Suggest you try method 3 in the following post.
http://forum.xda-developers.com/showthread.php?t=1622628
It does not require rooted TF. If you do everything right but still not working, you may have a faulty device.
^^ My peri runs that method, so that didn't work. :/
I think borked hardware, try NvFlash
just did this
ls - l /system/xbin/su
getprop ro.secure
returned: 0
So it is indeed set to 0.
NVflash.. well I would do that if I could get the usb connection to the computer working.. Still trying that.
Also, kokopopz
I went through method 3 on the tf itself, unfortunately it didnt work. Still trying to get adb working to try it that way.
simplywinter said:
I went through method 3 on the tf itself, unfortunately it didnt work. Still trying to get adb working to try it that way.
Click to expand...
Click to collapse
The following guide will be useful for setting up ADB.
http://forum.xda-developers.com/showthread.php?t=1071584
For the USB driver, you can try the naked driver.
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked
Note: I am a linux user. I set up ADB on my linux box. I did not try the above myself. I just came across them. They maybe useful to a Windows user.
Windows drivers are finicky, make sure you totally uninstall and reinstall them too. Took forever to get right on my computer.
no go with windows. I still cant seem to make this work... I have ubuntu on my laptop though. Can I even do this on Ubuntu? its 11.04
You can do this with Ubuntu no drivers required, just pick up the Nvflash wheelie for linux and get yourself a reflashed ROM.
Also you can still do this on TF. I had a very similar issue that I was able to fix by using Rayman's Blobtools (you can pickup blobunpack for windows in my bootsplash screen change guide).
Download the latest stock ROM for your device, and extract the 'blob' file out of it.
Put the blob in the same folder as blobunpack.exe, then open a command prompt and cd to the directory, then run:
Code:
blobunpack blob
After that you will see that there are now many blobs, one of them is called blob.EBT, this is your bootloader blob. What you want to do is copy that to /sdcard/ on your tf via mass storage or 'adb push blob /sdcard/' (You Have to remove the .ebt extension, it's just there as an ID, so it should just be 'blob')
Once that's there flash it through the staging partition (In terminal emulator or adb shell):
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
Then it shouldn't get stuck at the Eeepad screen anymore!
If it still does, you might have that weird problem where nothing flashed through staging partition sticks, so you'll need to run Roach2010's fix.
after trying that.. twice. It doesn't seem to stick. Roaches 2010 fix it is, searching for it right now.
If you can get adb shell access (I'm assuming yes) PERI has the fix bootloop option. Otherwise run roaches fix AFTER flashing a new recovery and EBT partition but BEFORE rebooting.
how do i run roaches fix. i Dont understand that part. I understand the rest though.
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.
When I try to power my phone, I get the LG logo then the phone immediately boots into TWRP and here I remain. I can not get into the down load mode to restore to phone to factory defaults. I did have the phone rooted, unlocked, TWRP installed, Flashify installed, and Goo Manager installed, as well as being SU enabled.
I had a backup of Flashify, but it is gone. I have a TWRP backup, but when I try to restore it, I am still stuck in the TWRP screen after I reboot.
Here is what happens. I select the restore of the file that I have on the phone and on the TWRP log screen, it shows the following:
Finished running boot script.
[Restore Started]
Restore folder: '/data/media/0/TWRP/BACKUPS/016d06d0ce078bbe/1970-01-02--04-03-34 JDQ39B'
Skipping MMD5 check based on user setting.
Restoring 7 partitions...
Restoring boot...
[Boot done (1 seconds)]
Restoring Recovery...
[Recovery done (0 seconds)]
Wiping System...
Removing all files under '/system'
Restoring System...
[System done (156 Seconds)]
Wiping Data...
Wiping data without wiping /data/media ...
Done.
Restoring Data
[Data done (79 seconds)]
Wiping Cache...
Removing all files under '/cache'
Restoring Cache...
[Cache done (1 seconds)]
Restoring EFS...
Restoring efs2...
[EFS done (0 seconds)]
Restoring efs2...
[efs2 done (1 seconds)]
Updating partition details...
[RESTORE COMPLETE IN 243 SECONDS]
After that, I get the Reboot System. I reboot the system and the result is: I get the LG G2 symbol and I go right back into the TWRP screen with the options of "Install" "Wipe" "Backup" "Restore" "Mount" "Settings" "Advanced" and "Reboot".
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
NevetsDrassel said:
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.....
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
Click to expand...
Click to collapse
Its funny and probably not a coincidence that this just happened to me two days ago. Fortunately, you have all the right safeguards installed and this should be an easy process.
Now, in mine, I had the exact same issue. What you will need to do is use either the terminal emulator on the twrp recovery menu or hook up the phone to your computer and use adb. There are only three lines of code to enter, one deleting the update, one disabling it's start, and one to clear the misc partition. I am currently in my phone now so I don't have the code but I will get on my computer soon and update with the code and it's source. Just make sure it is exact. Hold on a minute.
LG G2
livebyknight said:
Its funny and probably not a coincidence that this just happened to me two days ago. Fortunately, you have all the right safeguards installed and this should be an easy process.
Now, in mine, I had the exact same issue. What you will need to do is use either the terminal emulator on the twrp recovery menu or hook up the phone to your computer and use adb. There are only three lines of code to enter, one deleting the update, one disabling it's start, and one to clear the misc partition. I am currently in my phone now so I don't have the code but I will get on my computer soon and update with the code and it's source. Just make sure it is exact. Hold on a minute.
LG G2
Click to expand...
Click to collapse
Very much appreciated.
NevetsDrassel said:
Very much appreciated.
Click to expand...
Click to collapse
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
livebyknight said:
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
Click to expand...
Click to collapse
Within the folder that I have "what" in?
Got the drivers loaded and the system now recognizes an android device.
Started ADB
Copy and paste the code into "what" folder?
Thanks
Sorry I am new to this. Is this is what I was suppose to get?
C:\LG\Root Tools\ADB + Fastboot + Drivers>adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
~exit
# ←[6nadb rebootdd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fo
ta-backup.img
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 1.056265 seconds, 30.3MB/s
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/fota': No space left on devi
ce
65537+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 2.493231 seconds, 12.8MB/s
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on devi
ce
32769+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.675348 seconds, 23.7MB/s
~ # exit
C:\LG\Root Tools\ADB + Fastboot + Drivers>
And do I now reboot? or what?
Damn, it worked..... My phone is working again? Was this some type of virus or what?
Thank you thank you thank you for you assistance. You have saved me from the blackness of hell.
NevetsDrassel said:
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.
When I try to power my phone, I get the LG logo then the phone immediately boots into TWRP and here I remain. I can not get into the down load mode to restore to phone to factory defaults. I did have the phone rooted, unlocked, TWRP installed, Flashify installed, and Goo Manager installed, as well as being SU enabled.
I had a backup of Flashify, but it is gone. I have a TWRP backup, but when I try to restore it, I am still stuck in the TWRP screen after I reboot.
Here is what happens. I select the restore of the file that I have on the phone and on the TWRP log screen, it shows the following:
Finished running boot script.
[Restore Started]
Restore folder: '/data/media/0/TWRP/BACKUPS/016d06d0ce078bbe/1970-01-02--04-03-34 JDQ39B'
Skipping MMD5 check based on user setting.
Restoring 7 partitions...
Restoring boot...
[Boot done (1 seconds)]
Restoring Recovery...
[Recovery done (0 seconds)]
Wiping System...
Removing all files under '/system'
Restoring System...
[System done (156 Seconds)]
Wiping Data...
Wiping data without wiping /data/media ...
Done.
Restoring Data
[Data done (79 seconds)]
Wiping Cache...
Removing all files under '/cache'
Restoring Cache...
[Cache done (1 seconds)]
Restoring EFS...
Restoring efs2...
[EFS done (0 seconds)]
Restoring efs2...
[efs2 done (1 seconds)]
Updating partition details...
[RESTORE COMPLETE IN 243 SECONDS]
After that, I get the Reboot System. I reboot the system and the result is: I get the LG G2 symbol and I go right back into the TWRP screen with the options of "Install" "Wipe" "Backup" "Restore" "Mount" "Settings" "Advanced" and "Reboot".
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
Click to expand...
Click to collapse
Hey man im having the exact same problem, how do i exactly run the adb file? Im not sure if i still have it, what do i need to download, and when i did try it before it said my phone cannot be recognized, how did you fix your problem, can you walk me through please. Currently I am traveling and need my phone its useless right now.
fromc2m said:
Hey man im having the exact same problem, how do i exactly run the adb file? Im not sure if i still have it, what do i need to download, and when i did try it before it said my phone cannot be recognized, how did you fix your problem, can you walk me through please. Currently I am traveling and need my phone its useless right now.
Click to expand...
Click to collapse
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
NevetsDrassel said:
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
Click to expand...
Click to collapse
Wow thanks for the detailed instructions and explanations! ok sorry about this but what do you mean by koushes universal drivers?? where do i get those, and also paste the adb shell from which thread are you referring to? I will try this
---------- Post added at 11:41 AM ---------- Previous post was at 11:34 AM ----------
NevetsDrassel said:
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
Click to expand...
Click to collapse
I cant open the adb+fastboot drivers, it says windows cannot open. I have a windows 8 computer.
fromc2m said:
Wow thanks for the detailed instructions and explanations! ok sorry about this but what do you mean by koushes universal drivers?? where do i get those, and also paste the adb shell from which thread are you referring to? I will try this
---------- Post added at 11:41 AM ---------- Previous post was at 11:34 AM ----------
I cant open the adb+fastboot drivers, it says windows cannot open. I have a windows 8 computer.
Click to expand...
Click to collapse
You can get the Koush drivers from here.
You can get the script from http://www.photo-cool.com/?p=48043
Can't help you with Windows8. I know nothing about it. The ADB + Fastboot + Drivers is a .zip file. You have to unzip the file and put it on a directory of your choosing. I put my in C:/LG/ADB + Fastboot + Drivers/
Once you unzip the file (you can use 7Zip found here ) you will see the ADB.exe application along with 5 other .dll/applications/files in the folder.
livebyknight said:
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
Click to expand...
Click to collapse
This link is dead. Can you please give me another link? It's very urgent.
Just use this Toolkit
http://www54.zippyshare.com/v/29970713/file.html
Download D800 Rom and then add the .zip folder to Toolkit v1,5 - sideload folder
First you need to enter TWRP and then go to Advanced and press ADB Sideload Swipe
It's easier to rename it like rom.zip
Now start the start.bin
Select language
Enter
In my opinion it's 1 , enter
Then press 7) Install ROM/ Unbrick via SideLoad
Enter
and write the rom name that is in the sideload folder ( becouse i renamed it it's rom.zip in my opinion)
Now wait for the rom is pushin trough sideload
The installation process will start automatic .
I hope you got this by now,., had this happen to me...I found the thing to do..
On your TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and back out of terminal to reboot system
Help me plz same thing im facing with my lg g2
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
mehler said:
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
Click to expand...
Click to collapse
I am also in same situation. I have cyanogen recovery. haven't find any solution by readings in forums. biggest problem is my phone and adb server. adb shell never works. my phone is unauthorized. only work is sideload, but cannot install zip file. stuck every time on 47% and thee phone reboots and back to cyanogen recovery screen.
anybody had really solved this kind of problem.
any help is highly appreciated. there might be guys like me looking for solution.
Hi. My normal screen just been destroyed, and it's not a big problem 'cause I normally use the EPD screen for everything, but I need it for flashing, backuping or restoring ROMs. Even for a factory reset I need the LCD screen for the first start configuration.
There is a way to do it just using the eInk screen? As long I know, adb can't do that. Maybe just fastboot with his partition-by-partition backup can do that, but don't know how to do it.
I am wrong with the impossibility for doing that with adb?
Thanks
Still in this quest...
I reafirm myself in the impossibility of flashing with adb (as I think for sideloading you need a custom recovery). I tried with "fastboot -w update xxxx.zip" with the full FOTA of android 6 RU version, and it came to me the error of missing android-info.txt and android-product.txt. I think about getting them from another ROM for yotaphone2, but prefer to ask you before.
The other option is to flash every single partition with fastboot, which is easy, but I have to manage how to do it with the format that my FOTA has.
eReader Fan said:
Hi.
Click to expand...
Click to collapse
I think you are looking for the most difficult ways and are unlikely to find them,It's easier to get a new screen.
Sure, but a lot more expensive.
It is a long quest since I started, but I think I almost did it!!!
It will be nice if you achieve it to post a tutorial
I got same problem, or just didn't thought about that till I restored the phone and realised what I did!!
It should be possible to make the phone usable.
Seeing recovery on the back screen will never be possible I think unless a skilled person puts tons of work into making that work, but you don't really need it.
I found that you can skip the initial setup by manipulating the /system/build.prop.
So if you can get an adb shell with the system partition mounted writable, then you can edit the file to skip the setup which should make it possible to immediately use the mirroring mode....
Getting an abd shell should be possible by first going into fastboot mode(using power+voldown) and then booting twrp recovery ( https://forum.xda-developers.com/yotaphone-one/development/twrp-3-0-2-0-yotaphone-2-t3494023)
Code:
fastboot boot twrpimg.img
Then wait a little until twrp is booted (just wait for a minute)
then open an adb shell:
Code:
adb shell
then mount the system in writable mode and add the setup skip line to the build prop:
Code:
mount -rw system
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
and then reboot (still in adb shell):
Code:
reboot
I tested that you can go into twrp and mount the system writable but since I don't wanna reset my device, I cannot say for 100% sure that you will then be able to immediately use mirroring mode!
Also, for this to work, i think your bootloader needs to be unlocked. You can also do that using fastboot, but there is a next step which pops up on the normal screen, but it either just pressing power-button to confirm or pressing voldown of volup first and then pressing power to confirm you wanna unlock, so no touchscreen interaction needed. Beware that unlocking the bootloader erases userdata!
Lastly, you need to have fastboot and adb installed, go xda and google if you are not familiar enough with that.
Greets and good luck
tomgaga said:
It should be possible to make the phone usable.
Seeing recovery on the back screen will never be possible I think unless a skilled person puts tons of work into making that work, but you don't really need it.
I found that you can skip the initial setup by manipulating the /system/build.prop.
So if you can get an adb shell with the system partition mounted writable, then you can edit the file to skip the setup which should make it possible to immediately use the mirroring mode....
Getting an abd shell should be possible by first going into fastboot mode(using power+voldown) and then booting twrp recovery ( https://forum.xda-developers.com/yotaphone-one/development/twrp-3-0-2-0-yotaphone-2-t3494023)
Code:
fastboot boot twrpimg.img
Then wait a little until twrp is booted (just wait for a minute)
then open an adb shell:
Code:
adb shell
then mount the system in writable mode and add the setup skip line to the build prop:
Code:
mount -rw system
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
and then reboot (still in adb shell):
Code:
reboot
I tested that you can go into twrp and mount the system writable but since I don't wanna reset my device, I cannot say for 100% sure that you will then be able to immediately use mirroring mode!
Also, for this to work, i think your bootloader needs to be unlocked. You can also do that using fastboot, but there is a next step which pops up on the normal screen, but it either just pressing power-button to confirm or pressing voldown of volup first and then pressing power to confirm you wanna unlock, so no touchscreen interaction needed. Beware that unlocking the bootloader erases userdata!
Lastly, you need to have fastboot and adb installed, go xda and google if you are not familiar enough with that.
Greets and good luck
Click to expand...
Click to collapse
I might try it... It looks a little difficult for me.
But what bothers me is the unskippable tutorial from the beginning that shows you how to use the 2 screens...
Anyways I can always use it for spare parts
Hello guys,
Unfortunately I broke my 1+5's screen recently. I can barely see things on the bottom half of the screen and the touchscreen is not responding correctly so I can't unlock my phone anymore (cuz password is needed :good.
I would like to ship it back to 1+ factory so they can repair the screen but they will factory reset my device, this is why I'm requiring your help : I want to get some files which are inside my phone, but I don't know how to do it. I tried some things :
I have access to adb recovery but I'm unable to get su working : adb shell can't mount anything and ls shows nothing in data sdcard and so on.
I have access to adb unauthorized (unlock screen) and I tried to push adbkey.pub into /data/misc/adb/adb_keys with no success, still unauthorized.
In these 2 states adb pull /sdcard does nothing.
Any ideas ?
any solution?
gosuleaf said:
Hello guys,
Unfortunately I broke my 1+5's screen recently. I can barely see things on the bottom half of the screen and the touchscreen is not responding correctly so I can't unlock my phone anymore (cuz password is needed :good.
I would like to ship it back to 1+ factory so they can repair the screen but they will factory reset my device, this is why I'm requiring your help : I want to get some files which are inside my phone, but I don't know how to do it. I tried some things :
I have access to adb recovery but I'm unable to get su working : adb shell can't mount anything and ls shows nothing in data sdcard and so on.
I have access to adb unauthorized (unlock screen) and I tried to push adbkey.pub into /data/misc/adb/adb_keys with no success, still unauthorized.
In these 2 states adb pull /sdcard does nothing.
Any ideas ?
Click to expand...
Click to collapse
did you send it ?did they make factory reset to your phone?did you find any solution?
custom recovery ...
custom recovery have adb enabled, so boot twrp (it will ask for your password to decrypt data if their is encrypted, unfortunately : if so, I don't know sorry).
Nothing2Do.eu said:
custom recovery have adb enabled, so boot twrp (it will ask for your password to decrypt data if their is encrypted, unfortunately : if so, I don't know sorry).
Click to expand...
Click to collapse
You can decrypt the /data partition via adb, without using the touch screen.
The command you need is there:
https://forum.xda-developers.com/showthread.php?t=2484380
You can then adb pull /data/media to get your data.