I purchased a Kindle Fire HD 7 inch from a closing down sale attempted to flash a system.img to it to get it out of demo mode. Firstly i tried with the system recovery tool in these forums. I tried 3 different images, 7.1.5, 7.2.1, and 7.2.2. The last one causes the device to not even boot, the first 2 will boot to the start but there is no touchscreen so i can't do anything.
I've tried re-flashing the same images manually without using the recovery tool but it's the same situation. What has caused the touchscreen to not work and is it recoverable?
Thanks.
i had this problem too，you need to flash the other partions in addition to the system.img
if you cannot find them.try this : http://pan.baidu.com/share/link?shareid=140776&uk=906074556，its my backup without system for 7.1.5
Sent from my KFTT using xda premium
Hi, thanks for the reply, is it possible to tell me how to flash the other partition? I can't seem to find anything about it online. Also i don't know how to follow your link.
Thanks
EDIT: I worked out how to open your link. Silly me, i'll try it and see if it helps.
EDIT 2: THANK YOU SO MUCH! You fixed the problem for me, I'm very happy.
glad it helps.
Sent from my KFTT using xda premium
boot loop
longthinkzhang said:
glad it helps.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
hi do i just download file and is there then instructions to follow as i have same problem
bazm60 said:
hi do i just download file and is there then instructions to follow as i have same problem
Click to expand...
Click to collapse
download the file and extract them to ".img"
just change the two names in the code you used to flash the system.img
here is an example, when you are flashing the boot.img, use this:
Code:
fastboot -i 0x1949 flash boot boot.img
for more information：
http://forum.xda-developers.com/showthread.php?t=1930656
Newbie
longthinkzhang said:
download the file and extract them to ".img"
just change the two names in the code you used to flash the system.img
here is an example, when you are flashing the boot.img, use this:
Code:
fastboot -i 0x1949 flash boot boot.img
for more information：
http://forum.xda-developers.com/showthread.php?t=1930656
Click to expand...
Click to collapse
Hi this is all new to me. I did a factory reset and when complete touch screen would not work. I used the img restore from here. Now stuck on boot loop. So do you mean unzipp to this img file with system img in. And if so do I unzip all the other files. And then do I use the tool but write the command you have suggested. I am a bit baffled by this and have an expensive papper weight. Please a little more detail for a beginner. Thanks to all
bazm60 said:
Hi this is all new to me. I did a factory reset and when complete touch screen would not work. I used the img restore from here. Now stuck on boot loop. So do you mean unzipp to this img file with system img in. And if so do I unzip all the other files. And then do I use the tool but write the command you have suggested. I am a bit baffled by this and have an expensive papper weight. Please a little more detail for a beginner. Thanks to all
Click to expand...
Click to collapse
sorry for my bad english
have you flashed the system.img yet ? what's your system version before the boot loop?
you had a KFHD 7.2.2 or 7.2.3 and you flashed my .img files that belong to 7.1.5 , is that right?
if so , i would suggest you flash the 7.1.5 system.img now.
download it from here: http://pan.baidu.com/share/link?shareid=141429&uk=906074556 and then use the code below:
fastboot -i 0x1949 flash system system.img
when i said extract them to ".img", i meant that unzip them and you will get several ".img" files. >_<
boot loop
thanks for your responce, will yes kfhd 7 it was on 7.2.2 i did a factory reset and the touch screen never worked so i used the img restore tool on here and flashe with v2 and other v1.3 did not work, it was with 7.2.1 which came with v1.2, now stuck in boot loop, when you say enter code where am i entering it, thanks
when i say tool from here i mean the KFHD system.img recovery tool
I NEED AN IDIOTS GUIDE ON HOW TO FLASH THE OTHER PARTITION
update. i have flashed it with your image and it now starts but touch screen not working
Hmm......
i am sorry i am totally confused now and i donnot know how to tell you what to do in english. You may start a new thread and i believe somebody will help you.sorry again.
Sent from my KFTT using xda premium
bazm60 said:
thanks for your responce, will yes kfhd 7 it was on 7.2.2 i did a factory reset and the touch screen never worked so i used the img restore tool on here and flashe with v2 and other v1.3 did not work, it was with 7.2.1 which came with v1.2, now stuck in boot loop, when you say enter code where am i entering it, thanks
when i say tool from here i mean the KFHD system.img recovery tool
I NEED AN IDIOTS GUIDE ON HOW TO FLASH THE OTHER PARTITION
update. i have flashed it with your image and it now starts but touch screen not working
Click to expand...
Click to collapse
1. Download the File longthinkzhang showed me earlier.
2. Unzip all the files and put them somewhere you'll remember.
3. Create this folder C:\android-sdk-windows\platform-tools
4. Inside you need 4 files, (adb.exe) (fastboot.exe) (AdbWinApi.dll) (adbWinUsbApi.dll), they shouldn't be hard to find.
5. Put all the previously unzipped .img files in this directory.
6. Put the kindle into fastboot, open command prompt.
7. Type cd c:\android-sdk-windows\platform-tools
8. Type fastboot -i 0x1949 flash xxxx xxxx.img Replace the "xxxx" with the name of each file, example if it's dkernel.img type fastboot -i 0x1949 flash dkernel dkernel.img. Do the same for each file then reboot kindle and hopefully it works.
Solaris81 said:
1. Download the File longthinkzhang showed me earlier.
2. Unzip all the files and put them somewhere you'll remember.
3. Create this folder C:\android-sdk-windows\platform-tools
4. Inside you need 4 files, (adb.exe) (fastboot.exe) (AdbWinApi.dll) (adbWinUsbApi.dll), they shouldn't be hard to find.
5. Put all the previously unzipped .img files in this directory.
6. Put the kindle into fastboot, open command prompt.
7. Type cd c:\android-sdk-windows\platform-tools
8. Type fastboot -i 0x1949 flash xxxx xxxx.img Replace the "xxxx" with the name of each file, example if it's dkernel.img type fastboot -i 0x1949 flash dkernel dkernel.img. Do the same for each file then reboot kindle and hopefully it works.
Click to expand...
Click to collapse
So to reflash frome demo mode I need follow those steps? Right. How do I put it in fast boot mode? Do I need a cable or can I do it another way?
Thanks
Kindle Fire HD 7" Fastboot Mode
712m said:
So to reflash frome demo mode I need follow those steps? Right. How do I put it in fast boot mode? Do I need a cable or can I do it another way?
Thanks
Click to expand...
Click to collapse
712m,
Fastboot mode is enabled on the Kindle Fire HD 7" by using a "Factory USB Cable". You can order
one through the XDA User SkOrPn.
There are other cables out there but not the quality of SkOrPn, plus he is a really supportive member
of the XDA Community. Send SkOrPn a Personal Message with the Subject: Factory Cable Info Please
and include the ship to Country, nothing else (do not send him a long message about your problem). He
will reply with a PayPal invoice which you then place your shipping address, state, etc. After you place
the order he will send you support documentation that includes usage information. If you find yourself
backed into a corner, we offer free unlimited support and if you are really stuck we offer free phone
support, just send us a PM. We always post the results (solution) of the conversation on the XDA
Website so everyone can benefit. Get the cable, it is priceless. Then when it arrives, call us, we
will walk you through the restore step-by-step.
prokennexusa said:
712m,
Fastboot mode is enabled on the Kindle Fire HD 7" by using a "Factory USB Cable". You can order
one through the XDA User SkOrPn.
There are other cables out there but not the quality of SkOrPn, plus he is a really supportive member
of the XDA Community. Send SkOrPn a Personal Message with the Subject: Factory Cable Info Please
and include the ship to Country, nothing else (do not send him a long message about your problem). He
will reply with a PayPal invoice which you then place your shipping address, state, etc. After you place
the order he will send you support documentation that includes usage information. If you find yourself
backed into a corner, we offer free unlimited support and if you are really stuck we offer free phone
support, just send us a PM. We always post the results (solution) of the conversation on the XDA
Website so everyone can benefit. Get the cable, it is priceless. Then when it arrives, call us, we
will walk you through the restore step-by-step.
Click to expand...
Click to collapse
PM sent to SkOrPn
Follow Up - Feedback
712m said:
PM sent to SkOrPn
Click to expand...
Click to collapse
712m,
OK, great, this cable will make your Kindle Restore so easy. When it arrives, send us a PM,
we will be ready to help you and setup a phone or chat appointment. We are here 10:00am
to 10:00pm PST GMT -8. I will give my support staff a "heads up" so we are prepared to
get you online and restored quickly. We will supply you with a download link to download
clean system images. Do you want any options like Root, Google Play Store, Google
Applications, Go Launcher HD, Titanium Backup, etc. We can recompile the Image Files
to include these options, so when restored you will have a custom Turn Key Kindle.
All these options are free, just FYI.
Well now my kfhd is black doesn't power on. when I connect it with the SkOrPn cable and hold the power button I get the computer to some what see the device it flashes on and off as a omap444440.
Kindle Fire Factory Cable USB
bazm60 said:
thanks for your responce, will yes kfhd 7 it was on 7.2.2 i did a factory reset and the touch screen never worked so i used the img restore tool on here and flashe with v2 and other v1.3 did not work, it was with 7.2.1 which came with v1.2, now stuck in boot loop, when you say enter code where am i entering it, thanks
when i say tool from here i mean the KFHD system.img recovery tool
I NEED AN IDIOTS GUIDE ON HOW TO FLASH THE OTHER PARTITION
update. i have flashed it with your image and it now starts but touch screen not working
Click to expand...
Click to collapse
Solaris81,
Unfortunately when you attempt to flash the Kindle Fire HD with this method your
Kindle Fire HD will Brick, as you see. The problem is that you need a "Factory USB
Cable", this is mandatory. Contact SkOrPn to order the cable, please save yourself
more headachs and get the cable through SkOrPn do not buy it from Amazon, they
sell cheap Chinese cables that cause more problems than they fix. Once you get
the cable, send me a PM and we will supply you with the recovery image, step-by-step
on how to restore and if you need it we can supply phone support. Do not worry,
we will be here for you!
I got my SkOrPn cable and now it doesn't even power on now?Help
Kindle Fire HD 7" Dead
712m said:
I got my SkOrPn cable and now it doesn't even power on now?Help
Click to expand...
Click to collapse
712m,
Wow, I am sorry to hear this. Have you attempted to recharge the Kindle? Does the Kindle respond when you
plug in the charger? You should see a picture of a battery, anything? If no, you need to send it in for service.
Is the Kindle under warranty? If no, send it into our company, we have contacts at Amazon and may be able
to pull some strings to get you a replacement Kindle. If you need service, send it to our office:
Noob Series
Attention: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954
Main Line: (707) 774-5923
[email protected]
???
longthinkzhang said:
glad it helps.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
question how do you flash them with no custom recovery?
Related
Nvflash-ICS Restore!
This guide will not provide information to install Nvflash-ICS as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
The second method to restore has been removed until further study can be done!
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
I have finished installing Nvflash but where are my files?
/sdcard/AndroidRoot/ - this is your internal sdcard
Click to expand...
Click to collapse
What files should I have?
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
Click to expand...
Click to collapse
Nvflash recovery and going back to ICS for a fresh start.
Use blobunpack to unpack a stock ICS blob. The blob is found by unzipping the stock ICS firmware twice.
You can find the ICS firmware at this link (9.4.3.30) (post #3).
[INDEX][18 April 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
Please give philos64 a thanks while there, without him you would have a very hard time finding these downloads if at all.
these files have to be in the folder with Nvflash
wheelie -r --blob blob.bin -created with Nvflash install
nvflash --resume --download 4 blob.EBT -created with blobunpack
nvflash --resume --download 10 blob.APP – created with blobunpack
nvflash --resume --download 6 blob.LNX – created with blobunpack
nvflash --resume --download 5 recovery.img-ICS twrp recovery image name
nvflash --resume --go
then press volume down to enter twrp, flash root, flash rom or whatever you wish
Click to expand...
Click to collapse
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
What is blobunpack?
Here are some links to download and explain use.
https://github.com/AndroidRoot/BlobTools
windows compiled blobtools - http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
There were no dates for the following information.
The current AndroidRoot.mobi bootloader versions are
Transformer Prime: 9.4.2.28r01
Transformer TF300: 9.4.3.30r01
Transformer TF700:9.4.5.30r01
ChangeLog:-
Patch: Enable ‘fastboot boot’ command (removes ‘fastboot continue’, use ‘fastboot reboot’ instead).
Patch: Force unlocked state (protect your unlock status no matter what happens to your token).
Patch: Remove blob requirement from ‘fastboot flash’ (Flash the raw images (example: ICS_recovery.img) and not blob files).
Click to expand...
Click to collapse
When failing to get into APX mode you can try the following suggestions.
Special thanks to wha2do and daws for their input!
Also wha2do has posted a guide to enter APX that provides detail not found here! Please see his guide and give proper thanks if you find it helpful!
http://forum.xda-developers.com/show...3#post36159253
1.To enter APX mode you either have to boot, choose reboot (if available) and hold volume up pressed until it reboots and then the screen should remain black. Or if that doesn't work, completely shutdown your tablet and wait a second or two and then hold volume up pressed while pressing power on and keep it pressed until screen is blank.
or
2.fastboot -i 0x0B05 reboot (hold volume up)
or
3. adb reboot (hold volume up)
or
4. with unit powered on hold volume up and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
or
5. su
reboot -hold volume up.
This is done using a terminal; Android terminal is free from the play store. You must be rooted for this to work.
or
6. Another way:- Provided by daws
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.You should now be in APX mode.
Thanks for the help daws.
or
Only if there is no other resort!
7. remove cover from unit, disconnect battery, press and hold volume up, reconnect battery!
Click to expand...
Click to collapse
Good Luck!
Click to expand...
Click to collapse
Due to my dock smoking my motherboard I have purchased a new motherboard and luckily it came as 4.0.3 ICS.
I now have installed and use Nvflash on my tablet.
In case anyone is interested this is the unit I purchased.
The box shows - Manufacturer's Reconditioned Parts - 90 Day Limited Warranty.
Usefull guide
Good work and helpfull guide for xda members :good:
Nice stuff
philos64 said:
Good work and helpfull guide for xda members :good:
Nice stuff
Click to expand...
Click to collapse
Thank you for your kind words.
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
chanhny said:
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
Click to expand...
Click to collapse
No.
The files contain device-specific keys and cannot be used for other devices.
See the original thread for details:
[DEV][TOOL][BRICKPROOF]TF300 NVFlash release!
There's something I've not been quite clear about with NVFlash.
So I do my backup and keep my files.
Afterwards I upgrade to Jelly Bean (because I need the JB bootloader for ROM's right?), put TWRP recovery on, and flash a new ROM that uses the bootloader version I have.
So now I have the JB bootloader, can I still enter APX mode and do a restore, or do I have to remain on ICS bootloader to do a restore?
Is NVFlash truly unbrickable? A glance at this forum shows loads of bricks, would this have sorted their problem if they backed-up first?
Thanks!
tobdaryl said:
This guide will not provide information to install Nvflash as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
I have finished installing Nvflash but where are my files?
What files should I have?
Nvflash recovery and going back to ICS for a fresh start.
What is blobunpack?
Caution
Caution
There were no dates for the following information.
When failing to get into APX mode you can try the following suggestions.
Caution
Full brick recovery
Caution
Good Luck!
Click to expand...
Click to collapse
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
graphdarnell said:
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
Click to expand...
Click to collapse
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
tobdaryl said:
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
Click to expand...
Click to collapse
Not really. I didn't touch it. I'll do it again today to see. Thanks for the reply.
No recovery
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
waynestatemac said:
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
Click to expand...
Click to collapse
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
tobdaryl said:
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
Click to expand...
Click to collapse
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
waynestatemac said:
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
Click to expand...
Click to collapse
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
tobdaryl said:
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
Click to expand...
Click to collapse
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
waynestatemac said:
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
Click to expand...
Click to collapse
The first thing you flash in this guide is the bootloader. nvflash --resume --download 4 blob.EBT
With nvflash you can flash only what is needed for your situation. If you feel the problem is the bootloader you can flash just that and try again.
What you describe sounds like stock recovery is still working on your tablet. If flashing the bootloader does not help I would use stock 9.4.3.30, unzip once and place the remaining zip on your internal sdcard. You may get an update notification. Accept it and let your tablet do the work. If you don't get the notification reboot your tablet and you should see it then. Doing this will write stock bootloader, recovery, etc.
Stock recovery is the blob.SOS when you blobunpack. Just use the stock 9.4.3.30 blob and use the resulting SOS (recovery.img).
TF300T Bricked accessible using APX Mode.
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
NaderALDirany said:
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
Click to expand...
Click to collapse
I have read your previous posts in addition to this one.
There are four vehicles to restore your tablet. (some things can be done within android but you have no access)
1. recovery - stock or twrp
2. fastboot
3. adb
4. nvflash
I notice you also posted in my guide for accessing adb, fastboot, and apx. You were unable to access fastboot, adb, or recovery with those methods.
I don't know of any way to recover through apx without nvflash previously installed and you have no access to the other three methods.
Needs Stickied ... thanks man you helped save my butt :good:
Trigger911 said:
Needs Stickied ... thanks man you helped save my butt :good:
Click to expand...
Click to collapse
Thanks! *I'm glad you found the info useful.
hello i tried to download and flash paranoid ROM on my nexus 4 after some time i dnt like it so try to revert back to nexus 4 stock rom but something went very wrong and now my phone stock in boot loader
wen i try to switch on my phone it directly goes to boot loader i cnt do anything if scroll down and go to recovery my phone went black and its also not starting that.
wen try to connect my phone to computer to recover it ...most of the tool kits showing msg that u dnt have usb debugging on
Please help how to recover my phone
I had that issue once with when flash back from PA. I have to flash IMG files using a toolkit
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 08:06 AM ---------- Previous post was at 08:04 AM ----------
This is the took kit that I used and I had no debug on
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
Zehlek said:
I had that issue once with when flash back from PA. I have to flash IMG files using a toolkit
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Can u please tell me whice toolkit i should use and what is the procedure to do that many thanx
You'll have to do it the old fashioned way, i.e. use fastboot. If you're not familiar, don't rush it, research each step and ensure you have the drivers set up, adb and fastboot installed, etc...
Did you flash the stock recovery back on? IIRC once selecting Recovery from the bootloader you're presented with a black screen, and then must hold the power button for a second or two and then the stock recovery will show up. Limited options available however, wipe data, cache, etc...
http://forum.xda-developers.com/showthread.php?t=2010312
core81 said:
Can u please tell me whice toolkit i should use and what is the procedure to do that many thanx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
First select 1 to install drivers. Then download Google factory image and put Boot, System, Recovery in folder(to flash IMG files) in your toolkit folder. Then use option 11 to flash each one. Make sure you are in bootloader mode
axtzenswas
Zehlek said:
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
okay i ll try and get back to you..but should my computer can identify the device in boot loader mood?
any way i ll try the stock recovery method also and get back to you guys
many thanx for your time
core81 said:
okay i ll try and get back to you..but should my computer can identify the device in boot loader mood?
any way i ll try the stock recovery method also and get back to you guys
many thanx for your time
Click to expand...
Click to collapse
fastboot commands work from BL, adb doesn't. So long as the drivers are installed you will be able to see your phone.
https://developers.google.com/android/nexus/images#occam
That is the link to the factory images for the nexus 4.
http://forum.xda-developers.com/showthread.php?p=42407269
That is the fastboot you will need. (FOR WINDOWS)
turn off the phone and plug it in to fully charge it.
install fastboot
extract the files from the factory image into the fastboot folder.
turn on the device and leave it in the bootloader. (if need be turn off the device and hold vol up and down plus the power until you see bootloader)
run "fastboot devices", this will list any devices that fastboot sees. if your device is not in the list something more is wrong.
This images shows "adb devices" but it is the same output for "fastboot devices" https://sites.google.com/site/rodsmods13/_/rsrc/1370839220039/home/example screenshot.png
now run the "flash-all.bat"
dl200010 said:
...now run the "flash-all.bat"
Click to expand...
Click to collapse
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
CMNein said:
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
Click to expand...
Click to collapse
Yeah I completely forgot that! I don't have the image downloaded to look at to list the commands to install without using the bat file.
dl200010 said:
Yeah I completely forgot that! I don't have the image downloaded to look at to list the commands to install without using the bat file.
Click to expand...
Click to collapse
bat file is definitely the way to go however*, I've grown to hate typing terminal commands :laugh:
*Except for that one time I forgot to edit stuff
CMNein said:
bat file is definitely the way to go however*, I've grown to hate typing terminal commands :laugh:
*Except for that one time I forgot to edit stuff
Click to expand...
Click to collapse
I admin three Linux headless servers, so it is like second nature to me. Maybe best route for him is for one of us to modify the bat and post it.
Sent from my Nexus 4 using XDA Premium 4 mobile app
CMNein said:
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
Click to expand...
Click to collapse
my frnd can u please explain little bit more about the process
THANKS TO CMNein dl200010
MY PHONE IS BACK TO NORMAL
thanks alot
core81 said:
my frnd can u please explain little bit more about the process
Click to expand...
Click to collapse
One you have the factory image in hand and have the following files extracted to your platform-tools folder, you'll want to keep on opening the archives until you're left with the following, but don't extract anything from the zip file:
-bootloader-mako-makoz20i.img
-radio-mako-m9615a-cefwmazm-2.0.1700.84.img
-image-occam-jwr66y.zip
-flash-all.bat
You'll want to open the image .ZIP and delete userdata.img.
Then open the flash-all.bat and delete the -w as seen on line 23 in the screen capture.
core81 said:
THANKS TO CMNein dl200010
MY PHONE IS BACK TO NORMAL
thanks alot
Click to expand...
Click to collapse
Awesome, I see you got yourself sorted out while I was replying :highfive:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796
Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:
UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig
Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.
As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5
^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.
where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks
None of the above
Sent from my Nexus 5
Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:
finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers
THIS CURRENTLY DOESNT WORK. DONT TRY IT. JUST LEAVE THIS THREAD AND FORGET YOU EVER SAW IT.
Disclaimer: I take no responsibility for bricked devices. I will try to help you fix it if it happens.
But it really shouldn't happen.
This should root x.3.2.1, this isn't my work, this is Gran PC's work for the kindle fire HD 2013 (kfsowi) which runs the same software as the HDX, so this theoretically should work for The HDX's.
Prerequisites: fastboot cable, adb, and a half hour of your time
How to:
•Download the old update file (13/14.4.2.1) sadly, I don't have this, but if I find it, I will post it. I think the 13.3.1.0 is on my home computer, but I can't access it right now.
•Unpack it as a zip archive
•Find the boot.img and copy it into your working/adb directory (or just c:\ on windows)
•open a terminal window
•plug the powered on kindle into the computer with the fastboot cable.
•type: "adb reboot bootloader" without the quotes. Hit enter.
•type "fastboot -i 0x1949 flash boot boot.img" hit enter. Wait
•type "fastboot reboot" hit enter.
This is the tricky part. It will go past the first boot logo, but it *should* load a black screen. Now you cab root it with the old method because what we just did is roll back the kernel to the version that the root exploit will work on.
•once you root it with the old method for 13/14.3.1.0, type "adb shell su" and hit enter. If "#" pops up in your terminal window then you have root.
HOWEVER:
•There is still only a black screen, so now that we have root, we need to roll the kernel forward to the one from 13/14.3.2.1.
•Download the latest update for your device from Amazon's update webpage.
•unpack it like we did before with the old update.
•go to the boot.img we used before from the x.3.1.0 update. Delete it if it is in your adb/working directory. (or just c:\ on windows)
•copy the new boot-prod.img to your adb/working directory (or just c:\ on windows)
•type "adb reboot bootloader" hit enter.
•type "fastboot -i 0x1949 flash boot boot.img (again, be extra sure that this is the new one) hit enter
•type "fastboot reboot"
•the kindle *should* boot up as normal and be rooted. If it isn't, tell me, and I'll try to help you.
•Optional but recommended: install SuperSU, and update binaries.
Edit: I apologize for the boot-prod.img mix up. It is just boot.img it is apparently different for the HDX than the HD.
Reserved
Sent from my Galaxy Nexus using Tapatalk
What is the old update file version number? I found one from
s3.amazonaws.com[slash]kindle-fire-updates[slash]update-kindle-13.3.1.0_user_310079820.bin
Is that the right one for Fire HDX 7?
Or if possible, please upload the boot-prod.img somewhere so we can download.
Mineturtle33 said:
Disclaimer: I take no responsibility for bricked devices. I will try to help you fix it if it happens.
But it really shouldn't happen.
This should root x.3.2.1, this isn't my work, this is Gram_PC's work for the kindle fire HD 2013 (kfsowi) which runs the same software as the HDX, so this theoretically should work for The HDX's.
Prerequisites: fastboot cable, adb, and a half hour of your time
How to:
•Download the old update file (13/14.4.2.1) sadly, I don't have this, but if I find it, I will post it. I think the 13.3.1.0 is on my home computer, but I can't access it right now.
•Unpack it as a zip archive
•Find the boot-prod.img and copy it into your working/adb directory (or just c:\ on windows)
•open a terminal window
•plug the powered on kindle into the computer with the fastboot cable.
•type: "adb reboot bootloader" without the quotes. Hit enter.
•type "fastboot -i 0x1949 flash boot boot-prod.img" hit enter. Wait
•type "fastboot reboot" hit enter.
This is the tricky part. It will go past the first boot logo, but it *should* load a black screen. Now you cab root it with the old method because what we just did is roll back the kernel to the version that the root exploit will work on.
•once you root it with the old method for 13/14.3.1.0, type "adb shell su" and hit enter. If "#" pops up in your terminal window then you have root.
HOWEVER:
•There is still only a black screen, so now that we have root, we need to roll the kernel forward to the one from 13/14.3.2.1.
•Download the latest update for your device from Amazon's update webpage.
•unpack it like we did before with the old update.
•go to the boot-prod.img we used before from the x.3.1.0 update. Delete it if it is in your adb/working directory. (or just c:\ on windows)
•copy the new boot-prod.img to your adb/working directory (or just c:\ on windows)
•type "adb reboot bootloader" hit enter.
•type "fastboot -i 0x1949 flash boot boot-prod.img (again, be extra sure that this is the new one) hit enter
•type "fastboot reboot"
•the kindle *should* boot up as normal and be rooted. If it isn't, tell me, and I'll try to help you.
•Optional but recommended: install SuperSU, and update binaries.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I have the files needed but I can't find that boot-prod.img file, I have a boot.img and prod_cert_swap.sed in there on the 13.3.1.0 on the new one
mech_supernova said:
I have the files needed but I can't find that boot-prod.img file, I have a boot.img and prod_cert_swap.sed in there on the 13.3.1.0 on the new one
Click to expand...
Click to collapse
The Fire HD's update-kindle-11.3.1.0_user_310084920.bin contains boot-prod.img but the HDX's doesn't. (Also inside their 11.3.2.1 new update files, but not HDX's 13.3.2.1)
1. Not sure using HD's boot-prod.img would work or brick the HDX?
2. Or using HDX's boot.img directly would work?
Someone with better unbricking experience than mine should try it out.
I will attempt this, If someone can get me the link to download the previous update...
plasticarmyman said:
I will attempt this, If someone can get me the link to download the previous update...
Click to expand...
Click to collapse
Fire Kindle HDX's old update (contains only boot.img, no boot-prod.img):
s3.amazonaws.com[slash]kindle-fire-updates[slash]update-kindle-13.3.1.0_user_310079820.bin
Fire Kindle HD's old update (contains both boot.img and boot-prod.img):
s3.amazonaws.com[slash]kindle-fire-updates[slash]update-kindle-11.3.1.0_user_310084920.bin
the link for the 8.9" is https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.1.0_user_310079820.bin
i'm downloading it right now
EDIT: Downloaded and extracted....i have a boot.img should i try and flash that? @Mineturtle33
Mineturtle33 said:
Disclaimer: I take no responsibility for bricked devices. I will try to help you fix it if it happens.
But it really shouldn't happen.
This should root x.3.2.1, this isn't my work, this is Gram_PC's work for the kindle fire HD 2013 (kfsowi) which runs the same software as the HDX, so this theoretically should work for The HDX's.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Have you checked boot_prod against dkernel boot image in the HDX? IDK for certain, but I thought the 2013 HD was more akin to the HD 8.9 in terms of hardware, with the OMAP platform & the uboot based bootloader, (both of which are much easier to work with as there is a lot more documentation & reference). Aside from that, AFAIK, you cannot flash anything (signed or unsigned) via fastboot on the HDX, at least not with a locked bootloader. At any ratee, I am certain you can flash the older firmware using update, but you must alter the older version to reflect a newer version AND retain the signature. I have had limited success with this though, as it seeks some of the changes in the latest update alter the misc partition & make some changes in the trusted zone. These changes mean that even rolling back will cause some issues that can be a real pain. Location awareness is one. Connectivity is another. The you also have issue of audio not restoring locally whenever a headset or BT device is used. The same also hppens with video when switching back & forth from the device to a wireless display device.
EDIT: Yep. The new HD is indeed OMAP + uboot. This isn't going to work. Again, I am nearly 100% you cannot flash via fastboot period. If you could though, you may have a similar route via the initial boot.img, aka dkernel.img, but at that point, theere'd be no need anyway, since you'd have the keys or the required access via an unlocked bootloader.
GSLEON3 said:
Have you checked boot_prod against dkernel boot image in the HDX? IDK for certain, but I thought the 2013 HD was more akin to the HD 8.9 in terms of hardware, with the OMAP platform & the uboot based bootloader, (both of which are much easier to work with as there is a lot more documentation & reference). Aside from that, AFAIK, you cannot flash anything (signed or unsigned) via fastboot on the HDX, at least not with a locked bootloader. At any ratee, I am certain you can flash the older firmware using update, but you must alter the older version to reflect a newer version AND retain the signature. I have had limited success with this though, as it seeks some of the changes in the latest update alter the misc partition & make some changes in the trusted zone. These changes mean that even rolling back will cause some issues that can be a real pain. Location awareness is one. Connectivity is another. The you also have issue of audio not restoring locally whenever a headset or BT device is used. The same also hppens with video when switching back & forth from the device to a wireless display device.
EDIT: Yep. The new HD is indeed OMAP + uboot. This isn't going to work. Again, I am nearly 100% you cannot flash via fastboot period. If you could though, you may have a similar route via the initial boot.img, aka dkernel.img, but at that point, theere'd be no need anyway, since you'd have the keys or the required access via an unlocked bootloader.
Click to expand...
Click to collapse
At least on the HD you can flash anything with fastboot -- but if it is unsigned, it will fail to boot up (or sometimes actually just refuse to flash it). If it's properly signed, it should boot up.
I don't have an HDX to test with, but it seems to me like flashing the boot.img from an old update *may* work -- while you might not see anything on screen/some hardware may not work, you should be able to connect through adb and use the same old exploit -- and then revert to the newer kernel to get everything functional again. Again, I have not tested this so I cannot confirm it works, and I am assuming that fastboot would work. It is possible that it does not work as GSLEON3 described.
Similarly, you may have some success making a stripped down system.img that contains a su binary and flashing it, like I have done on the HD (again, no clue whether this will work on the HDX or not)
Gran PC said:
At least on the HD you can flash anything with fastboot -- but if it is unsigned, it will fail to boot up (or sometimes actually just refuse to flash it). If it's properly signed, it should boot up.
I don't have an HDX to test with, but it seems to me like flashing the boot.img from an old update *may* work -- while you might not see anything on screen/some hardware may not work, you should be able to connect through adb and use the same old exploit -- and then revert to the newer kernel to get everything functional again. Again, I have not tested this so I cannot confirm it works, and I am assuming that fastboot would work. It is possible that it does not work as GSLEON3 described.
Similarly, you may have some success making a stripped down system.img that contains a su binary and flashing it, like I have done on the HD (again, no clue whether this will work on the HDX or not)
Click to expand...
Click to collapse
So this won't work?
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
So this won't work?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
It *may* work if you use boot.img and not boot-prod.img (which doesnt exist), but it's probably not going to work.
I'll update the op.
Sent from my 2013 Kindle Fire HD
This thing is quickly reminding me of the lgF6 and L9 phones.
Sent from my SGH-T999 using Tapatalk
I tried to flash boot.img from the 14.3.1.0 bin file (Fire HDX 8.9) and unfortunately it didn't work. Attached is a screen capture of the command line output.
Here is the BIN file straight from amazon website couple of months ago, the 13.3.1 "update".
https://www.dropbox.com/s/98f9yxbmekwtxi2/update-kindle-13.3.1.0_user_310079820.bin
Also, I entered fastboot mode, but without a factory reset cable, my kindle displays KINDLE [fastboot]
and READY
but as soon as I attempt to flash boot.img file it says waiting for device...
Should I try with fastboot cable?
With it all that happens is the screen goes black, but I can hear it working, and it does indeed run out of battery.This is from previous experience of trying to unbrick it.
ferrouskid, it might be that you don't have your drivers set up correctly. When in fastboot your kindle should show up in device manager on windows as an Android Boot loader interface device.
I didn't use a factory cable, just a cable I have spare. I got a response from fastboot mode but flashing boot.img failed because the hardware/bootloader is locked down. See the attached screen capture on post #15.
Sent from my KFAPWI using XDA Premium 4 mobile app
---------- Post added at 09:06 PM ---------- Previous post was at 08:59 PM ----------
I should add please look past the first 6 lines of the screen capture on post #15. I typed the command in wrong the first time.
Sent from my KFAPWI using XDA Premium 4 mobile app
ggow said:
ferrouskid, it might be that you don't have your drivers set up correctly. When in fastboot your kindle should show up in device manager on windows as an Android Boot loader interface device.
I didn't use a factory cable, just a cable I have spare. I got a response from fastboot mode but flashing boot.img failed because the hardware/bootloader is locked down. See the attached screen capture on post #15.
Sent from my KFAPWI using XDA Premium 4 mobile app
---------- Post added at 09:06 PM ---------- Previous post was at 08:59 PM ----------
I should add please look past the first 6 lines of the screen capture on post #15. I typed the command in wrong the first time.
Sent from my KFAPWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're the first person I've seen who has gotten their computer to recognize the HDX in fastboot. I have tried multiple times and also always get waiting for device no matter what I do.
I forgot fast boot can't flash images >900 mb. Hmmm.
Mineturtle33 said:
I forgot fast boot can't flash images >900 mb. Hmmm.
Click to expand...
Click to collapse
It probably won't let you flash any image at all anyways. Else I could just make a reduced system image (the one I made for the HD 7 is 69 MB) that would give you root access.
Hi.
I was having trouble when I try to follow the method on essential's site.
Here's what adb told me:
"opening 'ota_file.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Did some research on google. But sadly still don't know how this happened. Plz, help me, if you know what to do. thx
I suggest trying to flash the stock dump OB3 from here:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
I assume you already unlocked the bootloader.
You will need to unlock critical as well, but if you got ADB up and running already, should be easy.
Download and unzip the OB3 dump.
Unzip and place all files where fasboot is placed, should be platform-tools.
fastboot flashing unlock_critical (will wipe entire phone)
Then run the flash-all.bat in terminal (you can just drag and drop the flash-all file into terminal)
If successful, run fastboot -w to format data just for good measure.
If unsuccessful, open the flash-all in a text editor and copy paste the commands one at a time in terminal, enter after each one.
If not able to get either to work, DO NOT REBOOT. ask for more help.
q13017 said:
Hi.
I was having trouble when I try to follow the method on essential's site.
Here's what adb told me:
"opening 'ota_file.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Did some research on google. But sadly still don't know how this happened. Plz, help me, if you know what to do. thx
Click to expand...
Click to collapse
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
jamesst20 said:
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
Click to expand...
Click to collapse
I just wait until the bts is available. I've had bad luck sideload in.
Sent from my PH-1 using XDA Labs
avd said:
I just wait until the bts is available. I've had bad luck sideload in.
Click to expand...
Click to collapse
I have gotten the essential today and the first thing I did is flash Android O and everything seems flawless
avd said:
I just wait until the bts is available. I've had bad luck sideload ing.
Click to expand...
Click to collapse
And if your bootloader is locked you can't fallback to other methods of your system goes wonky even if we have an a/b system.
Sent from my PH-1 using XDA Labs
Airwolf79 said:
I suggest trying to flash the stock dump OB3 from here:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
I assume you already unlocked the bootloader.
You will need to unlock critical as well, but if you got ADB up and running already, should be easy.
Download and unzip the OB3 dump.
Unzip and place all files where fasboot is placed, should be platform-tools.
fastboot flashing unlock_critical (will wipe entire phone)
Then run the flash-all.bat in terminal (you can just drag and drop the flash-all file into terminal)
If successful, run fastboot -w to format data just for good measure.
If unsuccessful, open the flash-all in a text editor and copy paste the commands one at a time in terminal, enter after each one.
If not able to get either to work, DO NOT REBOOT. ask for more help.
Click to expand...
Click to collapse
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
jamesst20 said:
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
Click to expand...
Click to collapse
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
q13017 said:
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
Click to expand...
Click to collapse
It only works with fastboot factory images. These are recovery flashable zip as far as I know.
Also, you need unlocked bootloader to flash factory images and in case you are already unlocked, you could just push the zip into your phone and use twrp to flash it.
q13017 said:
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
Click to expand...
Click to collapse
You could try booting your phone with usb debugging enabled and see if the command "adb push file.zip /sdcard/Download"
If this command fail aswell, it's probably driver related or cable. I don't think an invalid zip would make it fail
q13017 said:
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
Click to expand...
Click to collapse
The one that change with the phone is not for flashing
Sent from my PH-1 using XDA Labs
avd said:
The one that change with the phone is not for flashing
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Yeah, don't use the charging cable for flashing. Essential has confirmed that some phones have been bricked using their included cable.
Sent from my PH-1 using Tapatalk
jamesst20 said:
It only works with fastboot factory images. These are recovery flashable zip as far as I know.
Also, you need unlocked bootloader to flash factory images and in case you are already unlocked, you could just push the zip into your phone and use twrp to flash it.
You could try booting your phone with usb debugging enabled and see if the command "adb push file.zip /sdcard/Download"
If this command fail aswell, it's probably driver related or cable. I don't think an invalid zip would make it fail
Click to expand...
Click to collapse
Anyway, fastboot flash method works for me. There's a guy post the dumped image files above. Thx for your help!
q13017 said:
Anyway, fastboot flash method works for me. There's a guy post the dumped image files above. Thx for your help!
Click to expand...
Click to collapse
No problem! Then you had an unlocked bootloader
q13017 said:
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
Click to expand...
Click to collapse
Doesn't matter. If you use the fastboot method, you need to unlock the bootloader AND unlock critical, which will wipe user data anyway, unless you had already done that previously. You can try the sideload method with stock recovery, but if you're not able to get that to work, you don't have a choice but to unlock and try the fastboot method.
I'm trying to install Beta 3 (I'm coming from stock NMJ51B), but the sideload will end at 94% and I get the Message:
Unable to open sysfs usb node (no such file or directory) Trying configfs failed to set driver control: No such device
Install from ADB complete
The PH-1 will then boot just fine and everything seems to work.
Any ideas?
power-on+volume-up ..bootloader running?
Was problem solved?,I wanted looking for solved of same things.Just I found it's lost my process of running fastboot.