I have an issue with the recovery. I tried flashing a blob, a img different versions of twrp. after several failures I "erased" recovery, and flashed again. I tried adb dd... mmcblk8, no go. All that did was erase my system which was still booting until then. I wanted to use my nvflash backups but wheelie won't start either. I reinstalled the binairy too, no go. So then I tried using a blob file until I realized I have androidroot's bootloader. So the answer is flash the raw image of recovery and bootloader right, except no windows tool to do it. Also whenever I try to flash something, I no longer get the little blue line. If I try to use recovery now, I get this:
Update
blade2k11 said:
I have an issue with the recovery. I tried flashing a blob, a img different versions of twrp. after several failures I "erased" recovery, and flashed again. I tried adb dd... mmcblk8, no go. All that did was erase my system which was still booting until then. I wanted to use my nvflash backups but wheelie won't start either. I reinstalled the binairy too, no go. So then I tried using a blob file until I realized I have androidroot's bootloader. So the answer is flash the raw image of recovery and bootloader right, except no windows tool to do it. Also whenever I try to flash something, I no longer get the little blue line. If I try to use recovery now, I get this:
Click to expand...
Click to collapse
Now managed to sort out nvflash binaries to get into it. but I get stuck when trying to flash anything, because it looks like it can't find any partitions. I have a "factory-config.img" would that restore my partition table, and if so how to flash it in nvflash. By the way, it's now stuck in APX mode.
blade2k11 said:
Now managed to sort out nvflash binaries to get into it. but I get stuck when trying to flash anything, because it looks like it can't find any partitions. I have a "factory-config.img" would that restore my partition table, and if so how to flash it in nvflash. By the way, it's now stuck in APX mode.
Click to expand...
Click to collapse
If you have nvflash backups that you made then you should be fine.
Look at the following thread and if the beginning instructions doesn't fix you then try the automated linux recovery, That does everything.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
flumpster said:
If you have nvflash backups that you made then you should be fine.
Look at the following thread and if the beginning instructions doesn't fix you then try the automated linux recovery, That does everything.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Can you tell me what I'm doing wrong. I put all the files in the Home folder, after I copies and pasted the commands in terminal. chmod wheelie did nothing, then wheelie gives me an error: "./wheelie: 1: ./wheelie: Syntax error: word unexpected (expecting ")")".
If it makes a difference, I'm running this from an Ubuntu. Thx.
Edit: nevermind, I was using the wrong wheelie binairies.The ones in Craig 's help page doesn't seem to work I got it from androidrootmobi. Props to kdmd for his post on this issue. I got it to send bootloader; I just about got it working when the battery ran out. So now I have to wait for it to recharge. Bummer!
Finally I get it working but I get system.img too large for partition? I didn't have it so used the one from Unbricker v1.03. Any one have an idea about how to reslove this? Thx.
.com
FINALLY, I got it solved. I was searching online for another system.img when I found this other Guide for nvflash on FrAndroid.com THX to bobby.bobby2 Merci cousin!. Basically the same as Craiggomez except for one critical step that was missing, flashing the bricksafe.img first and foremost, which according to our french counterparts restores the bootloader. From then on just continue with the same order of files to restore from nvflash, or reboot to fastboot and use unbricker.
If you don't mind the french here's the link to bobby.bobby2's guide:
http://forum.frandroid.com/topic/143483-tuto-nvflash-tf201-activation-et-debrickage/
Related
I recently unlocked the bootloader and rooted the HTC Jetstream. I wanted to change the apns.xml file in the framework-res.apk. It's been awhile since I've done anything with an android device and I forgot to install CWM. I was in a rush and had done this a few times so I didn't think anything about it.
Now the tablet is stuck in a bootloop. I can get to HBOOT and therefore Fastboot, factory reset, etc. I even ran the factory reset but I'm still stuck in the bootloop. I came across this link so I could download a "stock" ROM, but the instructions call for CWM which I don't have. I was hoping that I could flash this ROM with Fastboot, but since I've never done this I wanted the opinion of an experienced Android user.
Thanks for your help in advance.
kylec8032 said:
I recently unlocked the bootloader and rooted the HTC Jetstream. I wanted to change the apns.xml file in the framework-res.apk. It's been awhile since I've done anything with an android device and I forgot to install CWM. I was in a rush and had done this a few times so I didn't think anything about it.
Now the tablet is stuck in a bootloop. I can get to HBOOT and therefore Fastboot, factory reset, etc. I even ran the factory reset but I'm still stuck in the bootloop. I came across this link so I could download a "stock" ROM, but the instructions call for CWM which I don't have. I was hoping that I could flash this ROM with Fastboot, but since I've never done this I wanted the opinion of an experienced Android user.
Thanks for your help in advance.
Click to expand...
Click to collapse
Can you get ADB to recognize you tablet at all?
ATT Intruder said:
Can you get ADB to recognize you tablet at all?
Click to expand...
Click to collapse
Unfortunately no. I think maybe the factory restore took away the USB debugging.
But since I have access to fastboot, I think I can flash a new system.img correct? And since I downloaded the "stock" ATT ROM it has the system directory. Only it isn't a system.img file.
I found another link that says this to create a system image like this:
sudo mkfs.cramfs temp/ system.1.5.img
sudo umount stock-system
sudo umount temp
So if I was to do this could I then flash via fastboot like this?
fastboot flash system system.img
Thanks for your time
Solved
My Jetstream is now back to normal. I used the information in this post.
Once I downloaded the files from the link I had to plug the tablet into my PC and put the it in fastboot mode and relock the bootloader "fastboot oem lock". The tablet turned off and I had to put it back into HBOOT mode. Run the .exe file that came with the download. Here I ran into a little trouble because the .exe file couldn't find my device. So I had to reinstall the drivers. After that just follow the prompts from the .exe file and I was good to go.
OK so I was on "HairyBean v2.31" and decided to try "CROMBi-kk". So I first flashed "TWRP-TF300T-2_7_0_1.zip" as instructed in the "CROMBi-kk" instructions. Then I flashed "CROMBi-kk" everything seemed to go fine but after reboot I was stuck at the "CROMBi-kk" boot animation. So I wanted to go back to "HairyBean v2.31" so flashed "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". When I got back to HairyBean TWRP I first tryed to Format DATA, well this got stuck and had no choice but to hard reboot. Now when I go back into TWRP I get a screen that asks for a password. I can hit cancel and get passed it, but I can't mount any of the partitions. So this is where in stuck. I do have an NVflash backup. Can someone please help me get out of this mess.
shatterstar78 said:
OK so I was on "HairyBean v2.31" and decided to try "CROMBi-kk". So I first flashed "TWRP-TF300T-2_7_0_1.zip" as instructed in the "CROMBi-kk" instructions. Then I flashed "CROMBi-kk" everything seemed to go fine but after reboot I was stuck at the "CROMBi-kk" boot animation. So I wanted to go back to "HairyBean v2.31" so flashed "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". When I got back to HairyBean TWRP I first tryed to Format DATA, well this got stuck and had no choice but to hard reboot. Now when I go back into TWRP I get a screen that asks for a password. I can hit cancel and get passed it, but I can't mount any of the partitions. So this is where in stuck. I do have an NVflash backup. Can someone please help me get out of this mess.
Click to expand...
Click to collapse
Try this:
Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes
If that doesn't work you'll have to recover through NVFlash backups.
Restorer said:
Try this:
Possible Unbrick Solution for Unrecoverable Bootloader & Wrong TWRP Flashes
If that doesn't work you'll have to recover through NVFlash backups.
Click to expand...
Click to collapse
Thanks i'll give that a try, but if that fails is their a guide on how to use NVflash to restore my backup? All I can find is how to backup using NVflash but nothing on restoring it.
shatterstar78 said:
Thanks i'll give that a try, but if that fails is their a guide on how to use NVflash to restore my backup? All I can find is how to backup using NVflash but nothing on restoring it.
Click to expand...
Click to collapse
There's plenty in these threads but read them right through carefully first. I've never bricked mine so I have no idea what problems you might encounter. The last two are older guides written before Flatline for JB but info is still relevant. Ignore any stuff about CWM or ROM Manager.
http://forum.xda-developers.com/showthread.php?t=2538028
http://rootzwiki.com/topic/35086-gu...s-guide-unbrickrecoverdowngradeupgrade-tf201/
Same guide but with XDA experiences:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Restorer said:
There's plenty in these threads but read them right through carefully first. I've never bricked mine so I have no idea what problems you might encounter. The last two are older guides written before Flatline for JB but info is still relevant. Ignore any stuff about CWM or ROM Manager.
http://forum.xda-developers.com/showthread.php?t=2538028
http://rootzwiki.com/topic/35086-gu...s-guide-unbrickrecoverdowngradeupgrade-tf201/
Same guide but with XDA experiences:
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
I can't tank you enough for your help in pointing me in the right direction. I'm now back up and running:good: The first guide got me close, but did not fully unbrick, so I got creative. I will list the steps I took to maybe help others out.
1. First you need Fastboot get it here(http://matthill.eu/content/downloads/transformerprime-unlock/fastboot.zip)
1b. You will need the Universal_Naked_Driver found here (http://matthill.eu/content/downloads/transformerprime-unlock/Universal_Naked_Driver_0.72.zip)
1c. Unzip the drivers somewhere, if at any point during this guide Windows detects your tablet as an unknown device, point it to this location for the drivers.
2. Unzip fastboot.zip somewhere preferably in C:\ (I found that folder names with spaces can cause problems)
3. Download the official update for your device from Asus. Make sure you get the right one, US, EU, WW, etc.
4. Unzip the update twice so that way you have a blob file.
5. Place the blob file into your fastboot folder.
6. Open a command prompt and navigate to your fastboot folder and enter the fallowing commands.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
This next command will take the longest. Also you will notice the green RCK icon will stop flashing and you will have a blue progress bar, This is normal. Do not run the last command(reboot) until the green RCK logo starts flashing again and the blue progress bar is full.
fastboot -i 0x0B05 flash system c:\fastboot\blob (your path may vary depending where you placed the fastboot folder)
Now that all is done run the last command.
fastboot -i 0x0B05 reboot
If you are back up and running congratulations you are unbricked, but if you are stuck at the white Asus logo follow the next additional steps. Only do this if you are not fully booting up after the first part of this guide.
1. You will need a microsd card(32G max) and has to be formatted to Fat32.
2. Next you are going to take the Asus update you downloaded above, and unzip it ONLY ONCE and rename it to EP201_SDUPDATE.zip
3. Place the newly renamed EP201_SDUPDATE.zip on your sdcard, make sure its on the root directory and not in a folder.
4. Now reboot to fastboot (Hold Power and Volume Down) Press Volume Up when the white text at the top appears.
5. When the fastboot menu comes up with RCK icon selected press Volume up.
6. Go have a beer, this will take some time. Do not touch anything, when it is done the Asus configuration wizard will be displayed.
7. Congratulations you are now hopefully fully unbricked.
Some Tips:
1. Make sure you have "Show File Extensions" enabled in Windows, if not then when you rename the update to "EP201_SDUPDATE.zip" it will actually be "EP201_SDUPDATE.zip.zip".
2. Use Windows 7 if possible, Windows 8 just causes problems.
3. Disable Windows UAC or run fastboot as administrator.
4. Use a stock OEM data cable.
5. Make sure you have a fully charged tablet, cant stress this enough if your battery dies during this process, then you are in some serious trouble.
Credit goes to Buster99 for discovering the first part of this guide.
Bricked my prime
Hello, I have a big problem. I am in the possession of a TF201 and wanted to install the slimkat-rom for the Tf201. I had the topical Bootloader with Harybean V2.31 installed.
Then I have the Recoery (form the Startpost of the rom) in my present Rocovery installed (Custom TWRP v2.7.1.0 JB/KK for TF300T [with device checking] | STABLE)
Afterwards I have restarted the device. Everything functioned perfectly... on it I have booted up in the Recovery. In it I made a Factory-Reset. This became not explained... the device approx. 1 hour got stuck.
On it there I have restarted the device by hand... now I have the problem that I do not come any more to the Recovery. The device hangs with the picture "Teamwin"... I can do nothing more....also i can not go into the fastboot mode!??? (with the volume down button)
I already tried the solution about abd...but in cmd (Windows) always comes the statement "waiting for device"
What have I wrong made... what I can make? Can somebody help me? Please....
sorry for my bad english, thanks
maze44 said:
Hello, I have a big problem. I am in the possession of a TF201 and wanted to install the slimkat-rom for the Tf201. I had the topical Bootloader with Harybean V2.31 installed.
Then I have the Recoery (form the Startpost of the rom) in my present Rocovery installed (Custom TWRP v2.7.1.0 JB/KK for TF300T [with device checking] | STABLE)
Afterwards I have restarted the device. Everything functioned perfectly... on it I have booted up in the Recovery. In it I made a Factory-Reset. This became not explained... the device approx. 1 hour got stuck.
On it there I have restarted the device by hand... now I have the problem that I do not come any more to the Recovery. The device hangs with the picture "Teamwin"... I can do nothing more....also i can not go into the fastboot mode!??? (with the volume down button)
I already tried the solution about abd...but in cmd (Windows) always comes the statement "waiting for device"
What have I wrong made... what I can make? Can somebody help me? Please....
sorry for my bad english, thanks
Click to expand...
Click to collapse
Did you do a NVflash backup before all of this happened? If you did you can follow this guide to unbrick http://forum.xda-developers.com/showthread.php?t=2538028
I think the problem is "TWRP v2.7.1.0". I'm going to look more into it to see if I can figure what the problem is.
Thank you so much for the instructions post above. If you figure out what went wrong with flashing that rom, I would like to know too.
dangoon said:
Thank you so much for the instructions post above. If you figure out what went wrong with flashing that rom, I would like to know too.
Click to expand...
Click to collapse
Well I made some progress, I figured out why I could not mount partitions. Turns out that when I hit "Format Data" and thought that it froze, well it did not freeze it just takes really long to finish(~30min). Now I can install it, but no matter what I try it all ways gets stuck at the 4 penguins on the latest version or the bootanimation on the older version. I have tried every combination of twrp recovery's, kernals and varies versions of the rom, but still no luck. I have tried probably every rom available for this tablet and this is the only rom that just refuses to install. From the sounds of some of the problems this rom has I really don't want to use it, but now im so pissed off that I have to figure out why the hell this thing is not working I just cant quit.
[UPDATE]
Ok got it all squared away. Everything all up and running. The second part of my problem (getting stuck at bootanimation) was caused by doing a factory reset before flashing. So the correct way to flash it is...
1. Make sure you are on the Hairy Bean Bootloader.
2. Make sure you are using a 2.7 TWRP.
3. First Format Data. (It will take long, about 30mins)
4. The go into Advanced Wipe and check everything except SDCard.
5. When it's finished reboot, If all went well you should only be at the bootanimation for about 5mins.
Also if you get the four penguins after reboot, then you did something wrong.
Perfect
Legthy, but OMG thank you very much,
thought I was screwed..
I had to do the second part as well, now I get the Asus Setup , to finalize .
Great work, Thanks again.
Madd Macc
Hey guys, after receiving my new Kindle Fire (ariel running 4.5.3) I followed steps 1-3 outlined here and managed to get TWRP installed and my Kindle rooted. Things started going wrong in step 4 however, when I followed the instructions linking to here, which then linked to here. Steps 6-8 of DeLooper's instructions are where I started to run into problems.
I installed the 4.5.4 update and then the SuperSU update and clicked reboot. I didn't see the "updating message" referred to in the instructions, instead the device just went into a boot loop. During this boot loop, I was still able to get the device into adb mode, and from there back into the TWRP recovery. I tried flashing the same file (with and without SuperSU) several more times with the same results. I also tried wiping the cache as well as doing a factory reset and still nothing.
After going back to the second link above (bibikalka's post), I downloaded the 4.5.4 update file he linked to from Dropbox in "Update 3" (which was different than the 4.5.4 update linked to by DoLooper). I then installed this file using TWRP and rebooted. At this point, my device went back into a boot loop, but now I am unable to access ADB or my recovery.
I still can get the device into fastboot, so I don't believe this is irrecoverable. I tried issuing the following:
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.8.6.0-ariel.img
however, the command just hangs and nothing happens as far as I can tell.
My guess is that my recovery/bootloader file(s) are to blame for my problems? I'm still fairly inexperienced with all of this, so any wisdom or direction anyone could provide would be GREATLY appreciated. Thanks!
So here's some additional information -
Like I mentioned above, I can get the device into Fastboot mode, but once I get there I can only send one "successful" command. The first command supposedly works but the second will just hang. Occasionally on the second command I'll get the following
ERROR: could not clear input pipe; result e0004051, ignoring...
ERROR: could not clear output pipe; result e0004051, ignoring...
Click to expand...
Click to collapse
So from here I can run
Code:
fastboot -i 0x1949 boot boot.img
and I get
downloading 'boot.img'...
OKAY [ 0.204s]
booting...
Click to expand...
Click to collapse
and that's where it sticks. I've also tried doing the same with the TWRP recovery image I've got and the same thing happens.
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
greenie01 said:
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
Click to expand...
Click to collapse
Sorry you're dealing with this. @bibikalka will have to give you a hand. Just wanted to mention that the difference between the two TWRP_ready update zips is not significant. (Explained here: http://forum.xda-developers.com/showpost.php?p=61771073&postcount=28 ) I linked to mine while b's was briefly unavailable.
Early on a couple people flashed update zip into recovery partition, but I'm not sure how that happened or if it could be the problem. Hang in there. Bibikalka can advise.
greenie01 said:
So here's some additional information -
Like I mentioned above, I can get the device into Fastboot mode, but once I get there I can only send one "successful" command. The first command supposedly works but the second will just hang. Occasionally on the second command I'll get the following
So from here I can run
Code:
fastboot -i 0x1949 boot boot.img
and I get
and that's where it sticks. I've also tried doing the same with the TWRP recovery image I've got and the same thing happens.
Does anyone have any suggestions of anything I can try? I've got nothing at this point, so they don't even need to be good suggestions . Is my Kindle hard bricked?
Click to expand...
Click to collapse
If you cannot boot into TWRP, I think you are done (Pwr & Vol+ during boot up). I wonder if somehow you have 4.5.4 bootloaders in there (instead of 4.5.3), because these would prevent you from booting into TWRP.
Try to get into TWRP, if not, call Amazon.
I seemed to have either bricked my 7840 or at the least it is stuck in a bootloop. It will startup with the Intel Inside logo and then just keep restarting over and over again. I can't get the recovery screen or anything. I've tried a few guides to unbricking on here but it doesn't stay on long enough to have files written to it.
Anyone have any advice on what I need to do?
BrettOutlaw said:
I seemed to have either bricked my 7840 or at the least it is stuck in a bootloop. It will startup with the Intel Inside logo and then just keep restarting over and over again. I can't get the recovery screen or anything. I've tried a few guides to unbricking on here but it doesn't stay on long enough to have files written to it.
Anyone have any advice on what I need to do?
Click to expand...
Click to collapse
Check my post.
http://forum.xda-developers.com/dell-venue/general/7840-freezes-tethered-cwm-bricked-t3171803
If you can stay on fastboot mode (power button+volume down), theoretically you can unbrick the device.
I actually did try that yesterday but I'll fiddle with it more over the weekend. Thanks!
bootloop help and reference links for Dell 7840 files
brettOutlaw or Wonglynn2004,
Did you have much success fixing the boot-loop? I was able to get my tablet rooted with social design concepts' droidboot files (1,2,3) and to unlock the bootloader, but managed to screw up my system to the dell boot-loop screen, by either installing busybox or erasing the wrong partition when trying to use Aparted on a 64gb card to get ext4.. At this point I still had access to CWM tethered.
I made it worse after flashing the ..BB.XML file below and I saw the blue USB image briefly, but still have fastboot. Fastboot screen details listed below as well as links to files and thread references. I hope I got all the references & source credit correct.
After using the flash_DDO_BB.xml to reset, and erasing for a clean start I no longer can get CMW tethered to work. The T4 Trigger has some write error / access problem. With fastboot I hope I can get this working again with some minimal help here. I am using an older Toshiba Win8 tablet and not sure about getting ADB fully setup. I used the Minimal ADB -Fastboot installer to fix an older TF700 (old asus transformer).
There were some suggestions for using dd to copy from the SD card to the System partition, but I don't know if ADB will work, or just fastboot commands in the current condition.
Does anyone have time for step by step instructions either using the Phone flash tool, or if I have to setup ADB and use dd to copy the boot.img and system.img?
I have the link at the end for someone with success using DD to copy from SD to the system partition. Thank you for any help or suggestions between the multiple sources below or order for applying Phone flash files.
-mrgardiner
Can someone make a Sticky for boot-loop resources for the Dell Venue 7840?
1. Phone Flash tool and which files to flash
2. social-design-concept and vampirefo for root process and Trigger T4.
3. xBIGREDDx boot.img and system.img files (dd copy vs phone flash tool)
4. Developer files from Dell.
5. anggusss OTA update.zip 5.1
6. Root files Droidboot
7. minimal ADB - Fastboot installer
OTA update.zip for 5.1 from anggusss
venue_8_7840_lollipop_OTA.zip
http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21
Developer edition files from Dell:
http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
xBIGREDDx system and boot img files
http://forum.datadevelopement.com/showpost.php?p=61173058&postcount=5
system.img: https://mega.co.nz/#!w9AjBCSI!YdQenTLDVVk0M9xx1LJT1OnKq5VhESgiyULA1FVIA8A
boot.img: https://mega.co.nz/#!Fk4FUSza!1gY1RjvnEI_HS0zk17WTHiywXFWc1VOCH-P2V5fVFPI
Someone with success using dd to copy above files:
http://forum.datadevelopement.com/d...-8-7840-developer-files-posted-t3144232/page3
Dell Flashphone tool:
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
http://forum.xda-developers.com/dell-venue/general/venue-8-7840-developer-files-posted-t3144232
venue_7840_droidboots.zip
https://mega.nz/#!E1oijRRC!U8MK5s8q0TPzWJPNoM9sHxfxjvGcF_sk20SN5YfAqzA
Tethered Temporary Recovery from Social designs vampinfo
https://www.androidfilehost.com/?fid=23991606952604606
Chainfires UPDATE-SuperSU-v2.46.zip
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
USB drivers from INTEL
https://software.intel.com/android/articles/intel-usb-driver-for-android-devices
Minimal ADB-Fastboot installer:
http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
Current fastboot screen info:
PRODUCT_NAME - BB
Variant - Venue 8 7840
HW_Version - unknown
Bootloader Version - unknown
IFWI Version - E004.F601
Serial Number - XXXXXXXXXX
Signing - unknown
Secure_Boot unknown
Made some progress
1. Went back to the earlier firmware without locked device.
venue_7840_droidboots.zip and used Phone flash tool with this ‘1-502_droidboot_and_firmware.xml’
2. used updated IntelAndroid-FBRL-07-24-2015.7z and got CWM back
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
3. Stuck trying to use ADB or fastboot, or CWM to load the boot.zip or boot.img and system.zip or system.img. CWM didn't recognize external SD after mounting. MIght have to be ext4 format?
mrgardiner said:
Made some progress
1. Went back to the earlier firmware without locked device.
venue_7840_droidboots.zip and used Phone flash tool with this ‘1-502_droidboot_and_firmware.xml’
2. used updated IntelAndroid-FBRL-07-24-2015.7z and got CWM back
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
3. Stuck trying to use ADB or fastboot, or CWM to load the boot.zip or boot.img and system.zip or system.img. CWM didn't recognize external SD after mounting. MIght have to be ext4 format?
Click to expand...
Click to collapse
Use Minimal ADB-Fastboot installer for boot.img.
I have tested and working.
Thank you,
I am stuck at 5.02. I get the OTA notice, but on reboot it hangs or does not load. After normal rebooting, it will ask to download the OTA again.
I went through a few combinations of droid boot 501, 502 and 5.1. At one point I had
'Encryption failed", but going back to the older droid boot worked. I have the OTA.zip, but I am not sure if it is possible to dd the sys.dat. An older thread said no go.
http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
Have you been able to get to 5.1 from dd an older system.img? I am not sure if I need to do a deeper formatting than enzymeyllw's post.
I see they replied to just flash the OTA in CWM. I will unroot and try that again. I don't remember the exact error code.
mrgardiner said:
Thank you,
I am stuck at 5.02. I get the OTA notice, but on reboot it hangs or does not load. After normal rebooting, it will ask to download the OTA again.
I went through a few combinations of droid boot 501, 502 and 5.1. At one point I had
'Encryption failed", but going back to the older droid boot worked. I have the OTA.zip, but I am not sure if it is possible to dd the sys.dat. An older thread said no go.
http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
Have you been able to get to 5.1 from dd an older system.img? I am not sure if I need to do a deeper formatting than enzymeyllw's post.
I see they replied to just flash the OTA in CWM. I will unroot and try that again. I don't remember the exact error code.
Click to expand...
Click to collapse
same thing happen to me. I use CWM to flash OTA.zip and end up with error 01.
Hi guys, after 10 hours of trying to get my P760 to life I finally, as a last resort, decided to open this threadh. Heres the deal, my friend gave me his P760 which was stuck at the boot logo, I firstly tried to fix it with LG mobile support tool but it got stuck at 15% after countless tries. Then I tried fixing it with Lg flash tool but it also gave me some errors "omap factory download fail lg p760". After that I couldnt access S/W mode anymore nor did the phone turn on, only black screen. When I connect it to my pc it just makes sounds of new device connected/disconnected. I tried this fastboot method http://forum.xda-developers.com/showthread.php?t=2292828 but couldnt make it work. Is the phone completely dead or is there anything more I can try? Any help is appreciated, thank you very much.
What was done to brick it in the first place?
Sent from my KYOCERA-C6745 using Tapatalk
I am not sure, my friend brought it to me and he didnt know the reason. Anyway I managed to get into fastboot on another computer and i tried to flash x loader and uboot with the bulit in options and i get the following error "FAILED (remote partition doesnt exist). What can I do next? Thank you for the reply.
EDIT I have tried to get the phone in S/W mode using this guide http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4 but I couldnt do it.
I am sure I have to flash something in fastboot so it would be great if someone could point me to exactly what. Thanks again.
EDIT 2 I tried to flash xloader and u boot from post #7 http://forum.xda-developers.com/showthread.php?t=2242444 and it gave me the remote partition error failed again. Is the phone "officially" dead?
My experience with this phone is that it is basically unbrickable, at least software wise, thanks to omap4boot. Fastboot is basically telling you the partition you specified doesn't exist. Check you are using the correct syntax. It should be fastboot flash u-boot u-boot.img and fastboot flash x-loader x-loader.img (I am assuming the files are named u-boot.img and x-loader.img).
Another possibility is that the partition table of the phone somehow got corrupted. In my opinion this is very unlikely, but it could happen if the phone is disconnected while flashing the GTP table with LGFlashTool. Let's hope that's not the case.
Good luck.
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Maha23 said:
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Click to expand...
Click to collapse
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
EdwinMoq said:
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
Click to expand...
Click to collapse
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Maha23 said:
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Click to expand...
Click to collapse
I'm seeing you using lelus method to fastboot...
1) Be sure you are in fastboot whith this command: fastboot devices
2) if the l9 is still in lg logo, just flash a recovery img into boot and recovery partition:
a) fastboot flash boot recovery.img
b) fastboot flash recovery recovery.img3)reboot the device, it must enter in recovery mode by force.
4) once in recovery just flash a custom rom as you wish
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
lecorbusier said:
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
Click to expand...
Click to collapse
Thanks for the reply. How do I perform the force hard reset? Yes, I couldnt get fastboot to work on win 10, on win 7 it works flawlessly.
Sent from my LG-D855 using XDA-Developers mobile app
Hello,
I have exactly the same problem with my p760, fastboot works so far but remote partition error and the phone stays always completely black.
Is there someone who has a new idea to fix it?
Hey,
I found this: http://massimoronca.it/2016/03/17/fastboot-failed-remote-partition-does-not-exist.html
but i dont really understand it, can someone help me?
Maha23 said:
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
readme again... try to flash a recovery.img into the boot partition
fastboot flash boot recovery.img
and then reboot... this foce the l9 to enter in recovery and then you can fotmat partitions in wipe options
---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------
Elsewhere you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
Hard reset is 10s power.
Such a swap of recovery and kernel could have happened after unbricking the phone, when the key combo for fastboot produces the LG recovery. That's why I flash stock twice, then it's right again & ready to root, install TWRP etc.
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Maha23 said:
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Click to expand...
Click to collapse
you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
puntoazul said:
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Srsly?
recovery partition image on boot?
Probably true. That would explain the strange behaviour of the key combos during boot, after unbricking the phone for the first time. The recovery has replaced the kernel, but the phone can still boot. Strange. Fastboot is unavailable, and the key combo for the recovery shows the "dead droid" and performs a factory reset.
Groszexxx said:
Srsly?
recovery partition image on boot?
Click to expand...
Click to collapse
Yes... is an effective method to boot by forced on TWRP or other recovery and then proceed to format all partitions and flash any rom consecutively. After flashing any rom the boot partition is rewrited by the boot.img of the rom.
I did this before on my own L9 for repair and other friends devices. Is totally safe
By the way, I'm not in warn