Develop Bugs

Sani N10 bricked while modding

Hello,
I have troubles with a Sanei N10 tablet. There was a problem during an update process, and it is not able to start. The problem is, the owner tried to force in a Clockworkmod recovery and a Cyanogenmod ROM via the fastboot.exe command "fastboot flash" using recovery.img and boot.img files. The only thing I can see on a regular boot is the Sanei logo, and then a black screen.
I managed to have fastboot.exe access by switching it on with the volume-down button pressed. I can see the device if I write "fastboot devices", and I am still able to flash the individual partitions with the same "fastboot partition file.img".
I tried myself to flash a CWM recovery and a Cyanogenmod rom, but I still have the same black screen. Then I tried to get the original rom, but I used a lot of files from a lot of forums and I still can not get out of this.
I have no access with Livesuit and Phoenixsuite to restore the tablet with, they are not able to see the device (adb.exe is not able to see it as well).
Have you any clue about how could I solve this?
A friend of mine has a working tablet identical to this one, is there any way to extract the partitions in .img format and to apply them to my device?
Thank you,
Jimmy

try this one askmefast.com/How_to_do_a_factory_reset_on_sanei_n10-qna4671741.html im 10 post user so cant add link.

[Q] Hardbrick after overwrite fastboot

Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks

I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/

EdoIsa said:
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
Click to expand...
Click to collapse
What are FZ DnX, IFWI, FW DnX and OS images files ?
How to extract them from the site you mentioned?
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....

I have no experience with FZ DnX, IFWI, FW DnX files, but the OS image file is on the site I posted.
Follow my link. Once there, expand the list 'Firmware' and download firmware Version WW_2.15.40.10. Once its downloaded, open the zip file. Inside should be a System.img file. Extract the System.img file into your Fastboot folder. This is the OS image the guide is referring to.
Ask around for the meaning of the other files. Meanwhile, I will research more about those files later tomorrow and get back with any info I can find. Good luck!

cde2006 said:
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
Click to expand...
Click to collapse
install driver manually. see attachment.

When you plug your phone into the computer, does the phone show up in the device management? Typing devmgmt.msc into the windows 7 start menu or the start run menu on XP is the fastest way to get to Device Manager.
Is the device already known by your computer?
What does device manager think it is?
If its unknown, please let us know what the Hardware Ids and Compatible Ids for this device show up as. In device manageer, you can open the devices properties and under the details tab choose Hardware Ids and Compatible Ids. you could screen shot these with Alt + PrtScn and use mspaint to save them off. Otherwise you have to use Ctrl + C to copy them out . You can choose all lines by selecting the first and while holding Shift, select the last. Then you can Ctrl + C to copy all of them out.

Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.

Chinaphonearena said:
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Click to expand...
Click to collapse
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.

I think that avoiding flashing droidboot and recovery, and making sure file hashes match, everything should be fine.

Same issue
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
cde2006 said:
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
Click to expand...
Click to collapse
I put my 64gb sd in my ZF2 that I originally partitioned for my LG Optimus Pro and I moved a bunch of apps to the SD with link2sd and the first time I rebooted, the same screen with the USB logo and a full progress bar showed up. It won't recognize any fastboot or adb commands even though the ASUS adb is showing up in device manager. Nothing else shows up. In devices and printers I get Moorefield. The phone randomly reboots and goes back to the same screen over and over and each time the asus adb disappears from device manager and then returns. I found a guide on the zenfone 5 that looks promising, using the intel flash tool, however it requires the ZenFone 2 raw firmware files and I can't find them... Hopefully someone could help me salvage my ZF2 cuz I was really beginning love the phone... Thanks ahead of time for anyone that looks into this for me!

i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.

sry, had only the files for V5. I will load down and put it here.

boot error and bricked zenfone 2
i have same problem with my phone please send moorefields or other intel based boot drivers.. tanks

please tutor how to fixed it, thanks for advice

cde2006 said:
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
Click to expand...
Click to collapse
Lol @ "got sequence on this forum" and "more safe proven way."
You didn't read the instructions carefully enough and made a big mistake as a result. The correct sequence was given. You just didn't read it carefully. Lesson learned.
Hopefully you can unbrick it.

No offense, but this type of thing is what happens when people just copy/paste and don't understand what they're doing.
What you did was overwrite the fastboot partition each time you flashed. You flashed a 2GB system img on top of your fastboot partition. This probably seemed like it locked up and you either unplugged or turned it off. This likely caused a corrupt partition.
Reading is key when you do anything with your phone.
This is perfectly safe. This is the way it works for all devices. It has nothing to do with the files or the phone. This was 100% user error. Simple as that.

ze550ml hard brick
http://forum.xda-developers.com/zenfone2/help/zenfone2-ze550ml-hard-bricked-t3148174#post61657126
my ze550ml hard brick too. please help me
sorry for bad english.

hardbrick zenfone 2
konsolen said:
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
Click to expand...
Click to collapse
Hello, i have the same issue with my zenfone 2, I download the firmware files from Asus website, but the Intel flash tool can't found a flashable image file. My question is to, if you have the firmware files that send it to me?

same issues here please help,

same issues here please help,

D855 Stuck at Boot Screen

So I think I've gone and bricked my LG G3.
After the ROM I was using, cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd) from here, kept freezing 20 seconds after startup, I went to update to cm-13.0-20160325-NIGHTLY-d855 (CM13 March 25th). I booted into recovery (TWRP 2.8.7.0) as usual and went to flash both the ROM's .zip file and an Opengapps .zip file using TWRP's queue feature. However, it appeared to get stuck at a line (unfortunately I don't remember what it said exactly. Something involving patching system, I think), so I pulled the battery. I get the feeling this was a super not good thing to do, as my G3 now sits at the "LG - Life's Good" screen indefinitely. Holding Power+Vol.Down does not boot into Recovery, and neither does holding Vol.Up and plugging into my computer activate Download mode.
I tried to be as thorough as I could with exactly the steps I took, so I'm just hoping someone can give me a few pointers on what I can do.
As I type this I had the phone connected to my computer next to me, and I've suddenly heard the Windows "Device connected" sound and the phone is now showing this in the top right corner, in tiny font:
Code:
[784670] Fastboot mode started
[784820] -- reset --
[784820] -- portchange --
Edit: When this occurred, a device named "Android" appeared under the "Other devices" tab in Windows Device Manager. It's got a yellow warning sign next to the icon, and Properties says that the drivers for the device aren't installed.
Perhaps this is relevant to getting it working again.

First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...

bender_007 said:
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
Click to expand...
Click to collapse
Many thanks for the reply.
By ADB drivers for the LG G3, do you mean the Lg United Mobile Driver? I have version 3.13.2 of them, if that's what they are.
When I input the commands
Code:
adb devices
or
Code:
fastboot devices
nothing appears, so are there different drivers I should look for?
I'm not too sure how to "fix" partitions, either, but I'm guessing it requires ADB/fastboot.
The file aboot.img and laf.img, will I need to find somewhere to download them from?
Again, I appreciate the response.

In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)

bender_007 said:
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
Click to expand...
Click to collapse
I used PdaNet to install the LG drivers, and inputting the command "fastboot devices" now shows
Code:
? fastboot
Inputting "adb devices" does not show anything, however.
I then attempted to flash a recovery, TWRP version 2.8.7.0 with the command "fastboot flash recovery "recovery.img"". However, the phone's screen showed the following:
Code:
[998960] Error: Command never completed
[998960] Error: Auto CMD12 Error
[998960] Error: Command never completed with errors
[998960] Failed Writing block @ 1
How do I fix the partitions and find the files "aboot.img" and "laf.img"?
Thanks for your help so far, I'm glad that there is progress now.

it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor

bender_007 said:
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
Click to expand...
Click to collapse
I retried the command fastboot flash recovery recovery.img but it resulted in the same output as before.
I followed the exact instructions to enter TWRP but it just stays at the LG logo screen. I've held Power+Vol.Down for about a minute after quickly releasing it+pressing it again at the LG logo, but it just doesn't do anything.
I've found myself a Lollipop KDZ file. The CyanogenMod I was running, however, ran on Android 6.0 Marshmallow. Will I need a Marshmallow KDZ file instead?

check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)

bender_007 said:
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
Click to expand...
Click to collapse
I appreciate the offer to use Teamviewer to help me, but I think it would be best if you typed out some instructions in a reply to this thread so that others with the same issue can refer to here.

Solution
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.

HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)

bender_007 said:
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
Click to expand...
Click to collapse
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.

HexManiacSpeck said:
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
Click to expand...
Click to collapse
No problem, sometimes you have to trust people
There were people who asked for help, installed teamviewer and didn´t gave any control permissions (which is fine). But they were expecting someone is having soo much free time to explain things (which I would if I had time)
cheers, flad you fixed it

Fixed my G3 I was about to send to trash!
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" fromhere, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Thanks a million for pointing to this recovery file!
I was also in a situation where all my attempts to flash a recovery were failing due to:
Failed Writing block @ 1
Click to expand...
Click to collapse
The rest of my phone was unusable (no working recovery, no download mode, just the LG logo or this fastboot mode)
I tried several TWRP recovery versions & flavors, but so far, I only successfully reboot in recovery using CyanogenMod recovery file (download.cyanogenmod.org/?device=d855). Though I was not able to do much afterwards apart some adb commands that were not working either.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p20
dd: /dev/block/mmcblk0p20: write error: I/O error
This recovery img did the trick and I'm now back with a CyanogenMod ROM and a wiped phone.

Installing Twrp issue!

Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo

You need a microsd card installed on the phone and a copy of twrp image on the microsd card - you can also add a copy of supersu zipfile if you want to install root
fastboot boot twrp-2.8.7.1-h811.img (phone itself boots TWRP)
from phone itself:
In TWRP hit Install > Images... (bottom right corner) > select TWRP.img on ext sdcard > select "recovery" > swipe for permanent install of twrp
for root: Hit the Home button > Install > select SuperSU zip on external sdcard > swipe
Reboot into Android. (if TWRP asks if you want to install SU, HIT NO!!!)
if you do not have an external sdcard to save SuperSU and the TWRP.img onto.. you will need to skip saving the files to sdcard until AFTER you fastboot OEM unlock and boot into TWRP. After fastboot booting TWRP you can use adb push to put SuperSU and TWRP.img onto the internal sdcard to install with TWRP. Or you can use the MTP mount option in TWRP and drag n' drop the files from the computer to the phone. You cannot store the files on the internal sdcard before the OEM unlock because OEM unlock wipes all your data.
These are for h811 g4 but should work fine for you, instructions can be found here:
https://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227

Dingo88 said:
Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo
Click to expand...
Click to collapse
You are using an abandoned version please use the latest beta in the official TWRP thread
.
Sent from my LG-H815 using XDA Labs

Dingo88 said:
Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo
Click to expand...
Click to collapse
i beleive win 10 gives problems and must use USB 2.0

Hi Cheers for replys,
Had an issue on Win7 where I couldn't make "android" drivers work, both LG usb and Google driver update failed miserably.
On the TWRP I've used the latest version and a previous version. Placed it within the ADB folder and on the SD card both came out saying , "invalid file destination or something like that" am I missing a command prompt for the phone to access the SD card?
Thanks Dingo88

Dingo88 said:
Hi Cheers for replys,
Had an issue on Win7 where I couldn't make "android" drivers work, both LG usb and Google driver update failed miserably.
On the TWRP I've used the latest version and a previous version. Placed it within the ADB folder and on the SD card both came out saying , "invalid file destination or something like that" am I missing a command prompt for the phone to access the SD card?
Thanks Dingo88
Click to expand...
Click to collapse
It seems you really miss something. Read carefully. Fastboot flash will not work!
You just need to reboot into bootloader then using
fastboot boot twrp.img
Then you should see TWRP. Then you would flash TWRP from within TWRP. That's all described in the official install guide.
Btw: Exactly because of your problems with drivers etc I created FWUL ( https://tinyurl.com/FWULatXDA )..
The latest TWRP beta is 3.1.1 btw.
.
Sent from my LG-H815 using XDA Labs

Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!

Dingo88 said:
Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!
Click to expand...
Click to collapse
Rename the downloaded twrp to twrp.img no dashes. and it has to be in the same folder where your adb exe is.
.
Sent from my LG-H815 using XDA Labs

Dingo88 said:
Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!
Click to expand...
Click to collapse
could be corrupted download verify md5 with latest 3.1.1 as named and downloaded using 61ed0c81afb750535bdb71dfb0298149 md5 key
then simplify things, rename file to twrp.img to avoid typing errors

Hi super newbie here please kindly help me root this phone

So I have hit a wall.
I have an old HTC One M8 - I want to root it and play with it.
I have Mint 19 installed on my old Thinkpad, I want to start learning Python and GO and doing things with Android.
So I successfully unlocked the bootloader last night I can't even remember how but I followed instructions and did it.
Now I am trying to root using TWRP and running into issues.
I have platform-tools on my desktop (I found it somewhere via these XDA Forums)
I have (I believe) a good TWRP HTC One M8 recovery image in that folder, named recovery.img
i got that through a link on here somewhere too.
I can successfully boot to the white text menu by restarting and holding power and volume down, and it says Fastboot USB
From there on my PC I open a command prompt in the platform-tools folder and put in the recommended command line:
fastboot flash recovery recovery.img (I have renamed it recovery.img)
It says it successfully flashed, but after this I cannot figure it out, it keeps booting to regular HTC start up screen.
I have SuperSU on the phone ready go to - I understand this would be the next step.
I also have the TWRP program on the phone but it doesn't do anything, the only thing I can do with it is download the iso for One M8 again.
Any ideas?
I am missing something here, I cannot boot into TWRP after its flashed.
Thanks