hello dear members.
i force restarted my tf700 in the middle of twrp formatting internal memory.after reboot twrp showed 0mb memory so i rebooted again and twrp just started to loop.i erased recovery, boot,misc,cach,system,user with fastboot.
i have no twrp to use adb command for getting partition blob file.
my device can go to bootloader but when ever i try to flash twrp recovery.img or stock blob file i get these errors:
most of all this one comes:
FAILED (command write failed (No such device or address))
other errors:time out or data transfer error(unknown error)
fastboot devices shows my device in the list but i get the errors.
i also had to rewire my data cable to a new usb2 connector head because i can't find new cable for my tablet in my country.as i have seen in the diagram tf700 only uses usb2 for data connection.
is my device hard broken or can it be repaired?
is it the cable?
please help me.
thank you
sx57 said:
hello dear members.
i force restarted my tf700 in the middle of twrp formatting internal memory.after reboot twrp showed 0mb memory so i rebooted again and twrp just started to loop.i erased recovery, boot,misc,cach,system,user with fastboot.
i have no twrp to use adb command for getting partition blob file.
my device can go to bootloader but when ever i try to flash twrp recovery.img or stock blob file i get these errors:
most of all this one comes:
FAILED (command write failed (No such device or address))
other errors:time out or data transfer error(unknown error)
fastboot devices shows my device in the list but i get the errors.
i also had to rewire my data cable to a new usb2 connector head because i can't find new cable for my tablet in my country.as i have seen in the diagram tf700 only uses usb2 for data connection.
is my device hard broken or can it be repaired?
is it the cable?
please help me.
thank you
Click to expand...
Click to collapse
I don't think that your device is hardbrick?
Maybe not the cable either.
Do you know the difference between "erase" and "format"? The answer may fix your device. Good lucks.......:fingers-crossed:
The tablet us not hard bricked, but the cable could be a problem. Do all fastboot commands fail? Including: fastboot reboot, fastboot format userdata?
If yes either the cable is bad or you hot wrong drivers....
If you can fix the fastboot problem you can get the tablet back.
berndblb said:
The tablet us not hard bricked, but the cable could be a problem. Do all fastboot commands fail? Including: fastboot reboot, fastboot format userdata?
If yes either the cable is bad or you hot wrong drivers....
If you can fix the fastboot problem you can get the tablet back.
Click to expand...
Click to collapse
If you interrupted the format process, your partition tables are screwed so you need to fix the partitions before trying to flash new blobs.... It is just my guesses for this issue. I hope that the user above has the latest bootloader so he can use the format cmd in fastboot. I believed that some older bootloader did not support the format cmd in fastboot and forgot started fromm what version that it added the format cmd...
Cheers,
LMK
Thank you all for kindly helping me.
Not all fastboot command fail.for example it cheerfully erased my recovery! And other partitions.
Take a look at this log when I tried to format system:
Creating filesystem with parameters:
Size: 805306368
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 3072
Label:
Blocks: 196608
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/49152 inodes and 6355/196608 b
erasing 'system'...
OKAY [ 2.317s]
sending 'system' (14616 KB)...
OKAY [ 4.666s]
writing 'system'...
OKAY [ 1.373s]
finished. total time: 8.379s
C:\Program Files (x86)\Android\android-sdk\platform-tools
sh system blob
sending 'system' (800927 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.007s
C:\Program Files (x86)\Android\android-sdk\platform-tools
As you see after system format I still can’t flash stock blob or recovery.if format user data fails at sending user data (second step after erase)but formar system completes successfully.
Any ideas what to do or how repartition the my tablet.
update: i also noticed that after every successful format system my device hangs at bootloader an d becomes unknown device so i have to reboot into bootloader again.every try at system blob flash comes with the mentioned errors in my original post.
C:\Program Files (x86)\Android\an
ta
Creating filesystem with paramete
Size: 61415620608
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14994048
Block groups: 458
Reserved block group size: 10
Created filesystem with 11/375193
erasing 'userdata'...
OKAY [ 38.151s]
sending 'userdata' (141163 KB)...
FAILED (data transfer failure (Un
finished. total time: 43.192s
C:\Program Files (x86)\Android\an
ta
Creating filesystem with paramete
Size: 61415620608
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14994048
Block groups: 458
Reserved block group size: 10
Created filesystem with 11/375193
erasing 'userdata'...
OKAY [ 38.392s]
sending 'userdata' (141163 KB)...
FAILED (data transfer failure (Un
finished. total time: 43.436s
every format userdata fails but format system succeeds.cache partition can be formatted too.
fastboot getvar all reports my bootloader locked! it's wiered.
ootloader) version-bootloader: 1.0
ootloader) version-baseband: 2.0
ootloader) version: 0.4
ootloader) serialno: 015d29955b43f613
ootloader) mid: 001
ootloader) product: Cardhu
ootloader) secure: yes
ootloader) unlocked: no
ootloader) uart-on: yes
ootloader) partition-size:bootloader: 0x0000
ootloader) partition-type:bootloader: basic
ootloader) partition-size:recovery: 0x000000
ootloader) partition-type:recovery: basic
ootloader) partition-size:boot: 0x0000000000
ootloader) partition-type:boot: basic
ootloader) partition-size:system: 0x00000000
ootloader) partition-type:system: ext4
ootloader) partition-size:cache: 0x000000001
ootloader) partition-type:cache: ext4
ootloader) partition-size:userdata: 0x000000
ootloader) partition-type:userdata: ext4
l:
nished. total time: 0.237s
sx57 said:
fastboot getvar all reports my bootloader locked! it's wiered.
ootloader) version-bootloader: 1.0
ootloader) version-baseband: 2.0
ootloader) version: 0.4
ootloader) serialno: 015d29955b43f613
ootloader) mid: 001
ootloader) product: Cardhu
ootloader) secure: yes
ootloader) unlocked: no
ootloader) uart-on: yes
ootloader) partition-size:bootloader: 0x0000
ootloader) partition-type:bootloader: basic
ootloader) partition-size:recovery: 0x000000
ootloader) partition-type:recovery: basic
ootloader) partition-size:boot: 0x0000000000
ootloader) partition-type:boot: basic
ootloader) partition-size:system: 0x00000000
ootloader) partition-type:system: ext4
ootloader) partition-size:cache: 0x000000001
ootloader) partition-type:cache: ext4
ootloader) partition-size:userdata: 0x000000
ootloader) partition-type:userdata: ext4
l:
nished. total time: 0.237s
Click to expand...
Click to collapse
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
You are using the "erase" and "format" interchangeable in your posts above so I am confused which cmd that you used in the fastboot mode. Did you use this cmd in fastboot?
Code:
fastboot format userdata
If not, then you can give it a try to see what is going on after that, good luck....:fingers-crossed:
LetMeKnow said:
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
You are using the "erase" and "format" interchangeable in your posts above so I am confused which cmd that you used in the fastboot mode. Did you use this cmd in fastboot?
Code:
fastboot format userdata
If not, then you can give it a try to see what is going on after that, good luck....:fingers-crossed:
Click to expand...
Click to collapse
thanks for answering.yes i used format userdata and i sent the log for it.it always finished in these 3 errors
1-no such device or address.
2-data transfer error
3-timeout
format system works well
top left of my tf700screen us written key driver not found..booting os and the some version information.
if i select rck or android i get unrecoverable bootloader error (0x0000000)in red color.i have no system or recover so the error is related to that i believe.before erasing recover it worked go into twrp which started looping.
i use erase when i use erase command and i use format when i use format command.sorry for causing confusion mate.
LetMeKnow said:
It is the first time that I hear that the bootloader is relocked.... Obviously, it is reported that your bootloader is still locked.
Click to expand...
Click to collapse
No, I get the same return with getvar all. And I guarantee you - my bootloader is unlocked
We have to remember that fastboot is a very generic Android tool... doesn't work the same on all platforms..
Probably
Code:
(bootloader) uart-on: yes
is the more relevant entry here. "Unlocking the bootloader" on this device is nothing more than gaining the ability to flash partitions with files not signed by Asus. The BL is still encrypted and proprietary....
sx57 said:
thanks for answering.yes i used format userdata and i sent the log for it.it always finished in these 3 errors
1-no such device or address.
2-data transfer error
3-timeout
format system works well
top left of my tf700screen us written key driver not found..booting os and the some version information.
if i select rck or android i get unrecoverable bootloader error (0x0000000)in red color.i have no system or recover so the error is related to that i believe.before erasing recover it worked go into twrp which started looping.
i use erase when i use erase command and i use format when i use format command.sorry for causing confusion mate.
Click to expand...
Click to collapse
Sigh...
Unfortunately you cannot really rely on fastboot return messages. Especially if you're trying this on Win10!!!!!!!
I'm getting totally frustrated with this OS. I get a positive return for "fastboot devices" and then it does nothing for any subsequent command. Gives me a "finished" for "fastboot reboot" but the tablet never reboots. Basically it does not respond to any fastboot commands.
Until I boot the tablet into recovery. Try a few adb commands - everything works. Go "adb reboot-bootloader" to get into fastboot mode and all the sudden all fastboot commands work???????????????
So that together with your patched cable introduces enough ????? that it's almost impossible to isolate the cause.
But the only way I have seen people (many, many people) recover from an "unrecoverable bootloader error" is by flashing the stock blob in fastboot. You gotta get that working.....
If you've tried this on a USB 3.0 port, try a USB 2.0. Reboot the PC, reboot the tablet when switching ports.
If you can get your hands on Linux machine, try that. Or try this live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Good luck!
berndblb said:
No, I get the same return with getvar all. And I guarantee you - my bootloader is unlocked
We have to remember that fastboot is a very generic Android tool... doesn't work the same on all platforms..
Probably
Code:
(bootloader) uart-on: yes
is the more relevant entry here. "Unlocking the bootloader" on this device is nothing more than gaining the ability to flash partitions with files not signed by Asus. The BL is still encrypted and proprietary....
Sigh...
Unfortunately you cannot really rely on fastboot return messages. Especially if you're trying this on Win10!!!!!!!
I'm getting totally frustrated with this OS. I get a positive return for "fastboot devices" and then it does nothing for any subsequent command. Gives me a "finished" for "fastboot reboot" but the tablet never reboots. Basically it does not respond to any fastboot commands.
Until I boot the tablet into recovery. Try a few adb commands - everything works. Go "adb reboot-bootloader" to get into fastboot mode and all the sudden all fastboot commands work???????????????
So that together with your patched cable introduces enough ????? that it's almost impossible to isolate the cause.
But the only way I have seen people (many, many people) recover from an "unrecoverable bootloader error" is by flashing the stock blob in fastboot. You gotta get that working.....
If you've tried this on a USB 3.0 port, try a USB 2.0. Reboot the PC, reboot the tablet when switching ports.
If you can get your hands on Linux machine, try that. Or try this live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Good luck!
Click to expand...
Click to collapse
thank you very much for helping me.i am using win7 my frirnd.
I am gonna do what you kindly suggested to see if i get it working.i will try to get another cable from someone if any of my friends have one by chance.is there a command to see if bootloader is really still unlocked?
I will post the results but getting a cable is gonna take a few days if possible at all.in the meantime i will try other solutions.thank you all my friends.please post if any othetr solution comes to your mind.
Don't worry. There's no way to lock the tablet again unless through Asus.
Watch the screen when you turn it on. Even in this state it should say: The device is unlocked
hellooooooooooooooooo.my tablet is alive and the problem is finally solved.thank you all my friends specially berndblb. i finlally found and bought a new cable and after some problems with different PCs(errors same as i mentioned in my original post) i succeeded.
here are some points that i think need to be emphasized upon:
a direct usb port was necessary for me.it worked when the device was connected directly to my Iconia (windows pc tablet) w700's only usb 3 port.(usb 2 works but a direct port is needed,hubs make more problems.)
in windows XP fastboot was completely useless and didn't work and would just stuck on commands.(most probably needed another driver)
look here please :http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Buster99's excellent solution needed to be done step by step.i had to erase the mentioned partitions and only after that,blob file was flashed successfully.
thank you all for your help.
Related
I tried flashing a new rom for my DS
on this forum:
update-saga-runnymede-s-v5.zip
unluckily
my phone just can turn on once, then it lagged for a long time.
i took out the battery and insert again. turn on again.
badly it lagged again. i repeated
then the third time it stucked at HTC white screen for about an hour
then i tried many times but failed
i try to updated the recovery
'updating recovery' <- this screen has been showing for mayb few hours ( i fell asleep while waiting, when i woke up it's out of battery. then i reboot again but in bootloader NO 'RECOVERY' option!
now my phone has this option but when i choose it it disappears!
so i couldn't flash new recovery through phone
HELP HELP I AM REALLY GETTING CRAZY OF THIS!
can anyone help?
Ok. It seems that your recovery is gone by some reason.
Since you are using adb, I suppose that you have fastboot command also.
Download this file, rename it to recovery.img. Reboot your phone to bootloader (vol down + power), connect it to PC. It should be "FASTBOOT USB" written on the screen. Then open command prompt and type:
Code:
fastboot flash recovery {path to the file}\recovery.img
It should take less than a second to flash it (if longer than you may have troubles with the eMMC chip). If ok reboot to recovery and flash a custom ROM.
If not OK, connect to PC again as described above and type:
Code:
fastboot getvar all
and post the output here.
firstly i haven't tried
Code:
fastboot getvar all
yet since i am still waiting for <waiting for device>
so mayb it has failed.
what should i do to end this and try another method?
close adb directly ?
here is the details when i try fastboot getover all
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Chris>fastboot getover all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Chris>
not getover, but getvar
copy the command from my post and paste it to your command prompt to avoid mistakes
EDIT: have you managed to flash the recovery?? the text in the brackets {} has to be replaced with the path to your file - e.g. C:\android
then the command will look like this:
fastboot flash recovery C:\android\recovery.img
sorry for that i missed the word
C:\Users\Chris>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.832.1
(bootloader) serialno: SH14MTJ01449
(bootloader) imei: 355067046266979
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3805mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
here's the result
is it possible that the chip fried while "all done"?
all seems ok. Have you managed to flash the recovery image. My previous post is updated, check it
sorry what do you mean your previous post? which is it?
cckwan said:
sorry what do you mean your previous post? which is it?
Click to expand...
Click to collapse
amidabuddha said:
EDIT: have you managed to flash the recovery??
Click to expand...
Click to collapse
the text in the brackets {} has to be replaced with the path to your file - e.g. C:\android
then the command will look like this:
fastboot flash recovery C:\android\recovery.img
oh now when i type
Code:
fastboot flash recovery C:\Users\Chris\Downloads\recovery.img
it shows:
Code:
sending 'recovery' <6000 kb>
OKAY [0.995s]
writing recovery...
then no continue action
staying here
what should i do the next?
Your next step is to go to the [GUIDE] Read this before going for eMMC replacement in my signature and follow point 4.1
Use this RUU
You will lose S-OFF and root, but eventually your phone will work again
how about my flash recovery still not yet complete...?
btw i am still trying to understand that post step 4.1
but i wanna know is it ok that recovery not yet finished?
4.1 If you have a 6.98.xxxx hboot
You probably already have the adb properly configured on your PC
Change your hboot with this one There are 3 ways:
i should download "this one" right? there are <Eng S-Off.rar> and <PG88IMG.zip> inside.
1) use the one click - it will flash it for you
what means by the 'one click"?
2) put PG88IMG.zip on your SDcard and rebot to bootloader. It will flash automatically. After flashing delete PG88IMG.zip from the SDcard
i can't see my sd card on PC, should i pull out the sd card to another phone and put in the files required then insert back to my phone ?
3) extract the image from PG88IMG.zip, rename it to hboot.img, connect the device to PC, reboot it to bootloader (it should be written "FASTBOOT USB" on the phone, open a command prompt on the PC and type:
sorry...
when i am installing ruu
error occurs: usb connection may lost
so wht can i do><
totally lost now
sorry... now i found i haven't flash hboot.img completely
as it showed: image update is bypassed!
so what should i do?
***updates***
i tried 'fastboot flash hboot G:\a1\hboot.img'
(tried:
http://forum.xda-developers.com/showthread.php?t=1236890
&
http://forum.xda-developers.com/showthread.php?t=1113820
then it showed
Code:
C:\Users\Chris>fastboot flash hboot G:\a1\hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.201s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.231s
---------------------------------------------------
cannot flash hboot to 0.98.2000 or what
----------------------------------------------------
i can see my serial no. on PC cmd by using 'fastboot devices'
but adb devices shows nothing
---------------------------------------------------
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
---------------------------------------------------
WHEN I choose 'recovery' option on fastboot it blacked for 0.1s then fastboot screen again without 'recovery' option
---------------------------------------------------
sleep time now 2:15am here
thank you very much amidabuddha reli so much!
you have done a lot i know but i just need some more help getting my DS turn on again...or there will be a murder news here which parents killed their son sosad
thank you. hope you can reply me ASAP when you are convenient!
--------------------------------------------------
i tried tpbklake'sadvice to flash a cwm recovery but the cmd stayed at writing recovery...
cckwan said:
***updates***
i tried 'fastboot flash hboot G:\a1\hboot.img'
(tried:
http://forum.xda-developers.com/showthread.php?t=1236890
&
http://forum.xda-developers.com/showthread.php?t=1113820
then it showed
Code:
C:\Users\Chris>fastboot flash hboot G:\a1\hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.201s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.231s
---------------------------------------------------
cannot flash hboot to 0.98.2000 or what
----------------------------------------------------
i can see my serial no. on PC cmd by using 'fastboot devices'
but adb devices shows nothing
---------------------------------------------------
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
---------------------------------------------------
WHEN I choose 'recovery' option on fastboot it blacked for 0.1s then fastboot screen again without 'recovery' option
---------------------------------------------------
sleep time now 2:15am here
thank you very much amidabuddha reli so much!
you have done a lot i know but i just need some more help getting my DS turn on again...or there will be a murder news here which parents killed their son sosad
thank you. hope you can reply me ASAP when you are convenient!
Click to expand...
Click to collapse
The Revolutionary HBOOT 6.98.1002 will not allow you to overwrite it. You can only overwrite it using a special version from Revolutionary/AlphaRevX for removing S-OFF and returning to S-ON. Search for Revolutionary return to S-ON.
sorry i am quite new in android
can u tell me how to find revolutionary?
i even dunno what type of file i should search
or can you give me the download link? please
tpbklake said:
The Revolutionary HBOOT 6.98.1002 will not allow you to overwrite it. You can only overwrite it using a special version from Revolutionary/AlphaRevX for removing S-OFF and returning to S-ON. Search for Revolutionary return to S-ON.
Click to expand...
Click to collapse
cckwan said:
sorry i am quite new in android
can u tell me how to find revolutionary?
i even dunno what type of file i should search
or can you give me the download link? please
Click to expand...
Click to collapse
Use the search function of this forum using the key word 'revolutionary s-on'
It should turn up a few threads that address the topic.
friend brought me a d820e to look at, says it happens after OTA (sounds weird...)
my analysis as follows:
1. bootloader stays locked after reboot, tried "fastboot oem unlock" several times
2. flashing factory image, custom recoveries, cache, etc... are failed
Code:
sending 'recovery' (9434 KB)...
OKAY [ 0.515s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.696s
.
3. factory reset/date wipe/cache wipe results in:
Code:
Can't mount /cache/etc...
i could try to flash with LG flashtool but i'm not sure which TOT i should use, don't want to brick the device even more.
any other suggestions?
device info:
Code:
tools>fastboot.exe getvar all
(bootloader) max-download-size: 0x40000000
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.22
(bootloader) version-bootloader: HHZ12d
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D820(E) 16GB
android system recovery LRX22C
sh33z0r said:
1. bootloader stays locked after reboot, tried "fastboot oem unlock" several times
Click to expand...
Click to collapse
eMMC is dead.
anything to do or just rma?
sh33z0r said:
anything to do or just rma?
Click to expand...
Click to collapse
If it's still in warranty, RMA. If it isn't, send it to LG and pay for repair (motherboard swap).
I'm going to post here to see if i can get any feedback.
mpgrimm2 said:
Well as I always say, I am not a developer or play one on TV...
My N5 locked up on me the other day after a call. I was on 5.1.1. LMY48B, basic stock with root going on a month or so since the 5.1.1 update which I did via full flash Method 2 originally (as all my updates).
- Phone stops at the "Google" screen.
- I can get to Fastboot, and I can get to factory recovery.
- I am lucky if I can get it to turn on at all so I can get to Fastboot screen; and when it locks, it takes a bit of a miracle to get it to turn off.
- I have been able to reflash the factory images from Post 1 with LMY48B 2x and went back and tried LMY47D for giggles. Same results.
It seems like something is corrupt with my /boot perhaps. Not sure if I should try a fastboot erase on all the partitions (EDIT: Tried that from post 2, no change) or if anyone has any other suggestions.
Click to expand...
Click to collapse
Edit:
As a last ditch i even tried WugFresh's N5 Toolkit just to see if it would somehow do something different on a stock reload. (LMY48B now)
Nope. No change.
Comes to a dead stop at the Google logo and just gets hot if i leave it there.
Really hoping someone knows something else to try so i can tuck the LG G4 away as a spare and get my N5 back.
Sent from my LG G4 on Tapatalk.
Bump.
Sent from my LG G4 on Tapatalk.
You have wiped data haven't you while trying this?
Sent from my Nexus 5 using Tapatalk
Ben36 said:
You have wiped data haven't you while trying this?
Click to expand...
Click to collapse
Yes. (I left out some of the details for C:/ .... boot.img etc below)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ...
fastboot reboot-bootloader ...
fastboot flash radio ...
fastboot reboot-bootloader ...
fastboot flash system ...
fastboot flash userdata ...
fastboot flash boot ...
fastboot flash recovery ...
Do you have a working nandroid backup to restore?
Did you try to format /cache instead of erasing it?
Primokorn said:
Do you have a working nandroid backup to restore?
Did you try to format /cache instead of erasing it?
Click to expand...
Click to collapse
I do have a backup on my pc. I can get to the bootloader, and run fastboot, load twrp but the backup still doesn't boot.
Tried flashing a zip of M preview2 someone put together with TWRP 2.8.7.1 . It hangs during install and phone shuts off.
* I don't think a format command has been done unless it was part of the factory image's script during during install.
I'm going to have to look up the syntax for a "fastboot format" after work unless you know it off hand? I assume its similar to the erase command.
Sent from my LG G4 on Tapatalk.
mpgrimm2 said:
I do have a backup on my pc. I can get to the bootloader, and run fastboot, load twrp but the backup still doesn't boot.
Tried flashing a zip of M preview2 someone put together with TWRP 2.8.7.1 . It hangs during install and phone shuts off.
* I don't think a format command has been done unless it was part of the factory image's script during during install.
I'm going to have to look up the syntax for a "fastboot format" after work unless you know it off hand? I assume its similar to the erase command.
Sent from my LG G4 on Tapatalk.
Click to expand...
Click to collapse
Yes, the same: fastboot format cache
Maybe you should add fastboot format userdata.
Primokorn said:
Yes, the same: fastboot format cache
Maybe you should add fastboot format userdata.
Click to expand...
Click to collapse
Well I did a format of: System, Userdata, & cache ... and an erase on the eMMC partitions (boot & recovery).
Code:
C:\Android\WorkingFlashFolder>fastboot format boot
Formatting is not supported for filesystem with type 'emmc'.
C:\Android\WorkingFlashFolder>fastboot format system
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'system'...
OKAY [ 1.320s]
finished. total time: 1.320s
C:\Android\WorkingFlashFolder>fastboot format cache
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'cache'...
OKAY [ 0.800s]
finished. total time: 0.800s
C:\Android\WorkingFlashFolder>fastboot format userdata
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
error: file_write: write: Bad file descriptor
Cannot read image.
erasing 'userdata'...
OKAY [ 7.970s]
finished. total time: 7.970s
C:\Android\WorkingFlashFolder>fastboot erase boot
erasing 'boot'...
OKAY [ 0.220s]
finished. total time: 0.230s
C:\Android\WorkingFlashFolder>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.230s]
finished. total time: 0.230s
Followed by a full load of the google factory images for LMY48B. Still hangs at the "Google" logo like something is corrupted in /boot or /aboot somehow? I'm not sure if there is anyway to actually delete/recreate the partitions on the N5 to get it to work. Still open to ideas.
Here is my "getvar" command output if its needed...
Code:
C:\Android\WorkingFlashFolder>fastboot getvar all
(bootloader) max-download-size: 0x40000000
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.26
(bootloader) version-bootloader: HHZ12h
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D820(H) 16GB
(bootloader) serialno: EDITED
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: yes
(bootloader) product: hammerhead
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1600000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1600000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 40000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 3321fa800
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 2bc00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:persist: 1000000
(bootloader) partition-type:persist: ext4
I ran out of ideas mate... Almost everyone in a similar situation had to send their device to Google.
I keep searching and come back to you if I find something useful.
Best of luck!
Bump. Tried latest LMY48i, still mostly dead.
It's clear to me that something is missing B/w the bootloader and the OS loader.
Open to ideas from some more knowledgeable folks, especially since I have had a few PM's from others in the same situation.
Sent from my LG G4 on Tapatalk.
Look here http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 you might have a corrupt persist partition.
Do you have usb debugging on?
Can you reach the phone with adb? (try "adb devices" command and see if it recognizes your phone).
Are you rooted?
I have the same problem, i have tried the persist solution but it does not work. it keep rebooting and its not the power button. thx for your help in adavnce.
eross said:
Look here http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632 you might have a corrupt persist partition.
Do you have usb debugging on?
Can you reach the phone with adb? (try "adb devices" command and see if it recognizes your phone).
Are you rooted?
Click to expand...
Click to collapse
Thanks for taking a look and sorry for the delay, my PC died Friday.
Yes I have taken a look at that thread hoping it would help. Unfortunately, no version of android back to the original release for my Nexus 5 will boot properly (req'd for the Persist T/S) to get past the Google logo which also prevents the use of ADB commands.
Fastboot/bootloader can be accessed (with difficulty) to reload the OS from the factory images, but always with the same result. No Go.
Special thanks to @diplomatic for finding an exploit that has the potential to target many MTK devices, which he originally wrote to target Amazon devices: Experimental Software Root for HD 8 & HD 10
With some tweaking, he got it to work on my Acer B3-A40 with an MT8167 chip and kernel 4.4.22. The result is getting a root shell on the device:
Code:
acer_asgard:/data/local/tmp $ ./mtk-su
New UID/GID: 0/0
acer_asgard:/data/local/tmp # id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
acer_asgard:/data/local/tmp #
The issue now is getting permanent root. From my understanding, because of dm-verity, I can't just mount /system as read/write to install su permanently. So I'm looking for help from you guys on how to proceed from here to get permanent root. And I think this is where it gets into specifics for each device.
On my particular device, nothing shows on screen in fastboot mode. If I run 'fastboot oem unlock', I can press any button on the device, but as soon as I press Vol+ it goes back to the prompt. But when I run 'fastboot getvar unlocked', it still shows "no". So I'm not sure how to proceed from here.
At the very least, I'm sure you guys can have some fun with this for other devices, but I am hoping to get some help with mine.
(As you can tell, I'm not super familiar with Android development. I am primarily a .NET developer, although I've dabbled a little in C/C++.)
Tagging the main contributors to the big Acer root thread in case you can help, or just want to have fun with this: @FireDiamond @vache @Shreps
A year later - any luck?
balexandrov said:
A year later - any luck?
Click to expand...
Click to collapse
Yeah, I did get it unlocked and rooted, through a roundabout way (a tool that diplomatic wrote). But I found out later that I can also try "fastboot flashing unlock". Apparently some tablets use that, including some Acer ones. It won't really make a difference on mine anymore since I'm already unlocked. And I don't want to re-lock and try it since I already modified the system partition and it'll probably brick my tablet.
So try that first. If "fastboot flashing unlock" doesn't work, then I can share the convoluted way.
balexandrov said:
A year later - any luck?
Click to expand...
Click to collapse
Hi, I'm interrested in rooting my B3-A40 permanently too.
Can someone confirm that it works with Amazing Temp Root for MediaTek ARMv8 [2019-12-28] and the "fastboot flashing unlock" command?
What else do I have to do to be rooted permanently?
Which guide I have to follow? I am not sure !
Do I have to install Magisk too?
Can you show me the correct steps please?
Thank you
BenchBox said:
Hi, I'm interrested in rooting my B3-A40 permanently too.
Can someone confirm that it works with Amazing Temp Root for MediaTek ARMv8 [2019-12-28] and the "fastboot flashing unlock" command?
What else do I have to do to be rooted permanently?
Which guide I have to follow? I am not sure !
Do I have to install Magisk too?
Can you show me the correct steps please?
Thank you
Click to expand...
Click to collapse
That temp root does work on this tablet, but to get permanent root, you need to unlock the bootloader. So try "fastboot flashing unlock" and see if that works for you.
cybersaga said:
That temp root does work on this tablet, but to get permanent root, you need to unlock the bootloader. So try "fastboot flashing unlock" and see if that works for you.
Click to expand...
Click to collapse
Should it be possible to install TWRP-Recovery and Custom-Roms after getting permanent root with Magisk and unlocking the Bootloader?
I ask this because of the VM-Verity .
BenchBox said:
Should it be possible to install TWRP-Recovery and Custom-Roms after getting permanent root with Magisk and unlocking the Bootloader?
I ask this because of the VM-Verity .
Click to expand...
Click to collapse
I'm not aware of anyone who has ported TWRP to this tablet, or made a custom ROM. I just have permanent root via Magisk.
Once you unlock the bootloader, DM Verity isn't an issue anymore. That's your first step. Have you tried to see if "fastboot flashing unlock" works yet?
cybersaga said:
I'm not aware of anyone who has ported TWRP to this tablet, or made a custom ROM. I just have permanent root via Magisk.
Once you unlock the bootloader, DM Verity isn't an issue anymore. That's your first step. Have you tried to see if "fastboot flashing unlock" works yet?
Click to expand...
Click to collapse
O.K. then I would try it.
Can you please confirm the order of steps that nothing goes wrong?
1.) Amazing Temp Root for MediaTek ARMv8 [2019-12-28]
2.) Then I get the Bootloader unlocked with your command "fastboot flashing unlock" (if it is possible for me)
3.) After unlocking Bootloader I can install Magisk with Get full root with Magisk on a locked bootloader! ?
Is this the right way of getting it running permanently?
Sorry for so much questions but I am a little bit unsure.
Thank you.
cybersaga said:
Yeah, I did get it unlocked and rooted, through a roundabout way (a tool that diplomatic wrote). But I found out later that I can also try "fastboot flashing unlock". Apparently some tablets use that, including some Acer ones. It won't really make a difference on mine anymore since I'm already unlocked. And I don't want to re-lock and try it since I already modified the system partition and it'll probably brick my tablet.
So try that first. If "fastboot flashing unlock" doesn't work, then I can share the convoluted way.
Click to expand...
Click to collapse
I have give it a try but "fastboot flashing unlock" do not work for me, pls share the convoluted way, thx.
Code:
PS C:\WINDOWS\system32> fastboot flashing unlock
...
OKAY [183.578s]
finished. total time: 183.578s
PS C:\WINDOWS\system32> fastboot getvar unlocked
unlocked: no
finished. total time: 0.000s
BenchBox said:
I have give it a try but "fastboot flashing unlock" do not work for me, pls share the convoluted way, thx.
Code:
PS C:\WINDOWS\system32> fastboot flashing unlock
...
OKAY [183.578s]
finished. total time: 183.578s
PS C:\WINDOWS\system32> fastboot getvar unlocked
unlocked: no
finished. total time: 0.000s
Click to expand...
Click to collapse
Hi Normally Unlocking the bootloader is easy on most MediaTek's although I have not tried it with any Acer devices and especially this 4.4 kernel version.
The standard way is as follows so do each step in order.
1. Go to /settings/about device/ and tap build number seven times till you get the "You are Now a Developer" toast then press the back button
2. Got to /settings/developer option (this is a new menu item BTW)/You should see "OEM Unlocking" if allowed slide it to on along with usb debugging.
3. You can now try adb reboot bootloader or adb reboot fastboot if niether of those bring you to fastboot reboot to stock recovery and choose fastboot mode from the stock recovery option.
4. OEM's use their own cmds so this could be tricky part. In fastboot try the standard "fastboot oem unlock" or "fastboot flashing unlock" You will need to reboot after each before the Var becomes updated. To be honest it looks like the "fastboot flashing unlock" worked so double check the var after reboot to fastboot.
Your userdata should be wiped on reboot so if it is then the unlocking worked regardless of the Var some of the OEM bootloader unlocking implementation are a little flaky and some are just simply broke so dont always expect a nice read out. :laugh:
On alot of MTK devices simply signing the custom boot.img with AVB is enough to fool the bootloader so no need to unlock the bootloader at all. :fingers-crossed:
PS: Use the [ fastboot getvar all ] cmd we do with seeing if the "secure" var is set too.
.
bigrammy said:
Hi Normally Unlocking the bootloader is easy on most MediaTek's although I have not tried it with any Acer devices and especially this 4.4 kernel version.
The standard way is as follows so do each step in order.
1. Go to /settings/about device/ and tap build number seven times till you get the "You are Now a Developer" toast then press the back button
2. Got to /settings/developer option (this is a new menu item BTW)/You should see "OEM Unlocking" if allowed slide it to on along with usb debugging.
3. You can now try adb reboot bootloader or adb reboot fastboot if niether of those bring you to fastboot reboot to stock recovery and choose fastboot mode from the stock recovery option.
4. OEM's use their own cmds so this could be tricky part. In fastboot try the standard "fastboot oem unlock" or "fastboot flashing unlock" You will need to reboot after each before the Var becomes updated. To be honest it looks like the "fastboot flashing unlock" worked so double check the var after reboot to fastboot.
Your userdata should be wiped on reboot so if it is then the unlocking worked regardless of the Var some of the OEM bootloader unlocking implementation are a little flaky and some are just simply broke so dont always expect a nice read out. :laugh:
On alot of MTK devices simply signing the custom boot.img with AVB is enough to fool the bootloader so no need to unlock the bootloader at all. :fingers-crossed:
PS: Use the [ fastboot getvar all ] cmd we do with seeing if the "secure" var is set too.
.
Click to expand...
Click to collapse
Thanks for your help,
if i give the "fastboot flashing unlock" command it looks like this in the CMD:
Code:
C:\Minimal ADB and Fastboot>fastboot flashing unlock
...
But the problem is that i can't see something on the screen of the device because in bootloader-mode the screen is black!
If I push the "Power" or the "Vol -" Buttons on the device nothing is changing.
But if i press "Vol+" it comes back in the CMD:
Code:
C:\Minimal ADB and Fastboot>fastboot flashing unlock
...
OKAY [1034.731s]
finished. total time: 1034.733s
C:\Minimal ADB and Fastboot>
then i give the "fastboot reboot" command and it's rebooting:
Code:
C:\Minimal ADB and Fastboot>fastboot flashing unlock
...
OKAY [1034.731s]
finished. total time: 1034.733s
C:\Minimal ADB and Fastboot>
Now we have a look at the "fastboot getvar all" command:
Code:
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 292380000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: ed000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2100000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 60000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:persist: 3000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: NEOSTRA8167_TB_N
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.153s
C:\Minimal ADB and Fastboot>
"secure: yes"
Thank you for helping me.
What else can i do know?
BenchBox said:
Thanks for your help,
But the problem is that i can't see something on the screen of the device because in bootloader-mode the screen is black!
If I push the "Power" or the "Vol -" Buttons on the device nothing is changing.
But if i press "Vol+" it comes back in the CMD:
Click to expand...
Click to collapse
A blank screen is not uncommon as long as you get the reply on you cmd prompt then it's OK as I doubt you will need to confirm anything on the device :fingers-crossed:
BTW what version of Fastboot are you using in Minimal ADB and Fastboot?
Running
Code:
fastboot --version
in the cmd prompt should tell you the version and the location from which it's been run. (Post the output of that cmd) A up to date fastbboot.exe is recommended along with up to date drivers. :good:
BenchBox said:
Code:
C:\Minimal ADB and Fastboot>fastboot flashing unlock
...
OKAY [1034.731s]
finished. total time: 1034.733s
C:\Minimal ADB and Fastboot>
then i give the "fastboot reboot" command and it's rebooting:
Now we have a look at the "fastboot getvar all" command:
Code:
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 292380000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: ed000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2100000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 60000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:persist: 3000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1[/HIDE]
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: NEOSTRA8167_TB_N
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.153s
C:\Minimal ADB and Fastboot>
"secure: yes"
Thank you for helping me.
What else can i do know?
Click to expand...
Click to collapse
Can you use SPFlashTool on the device?? I know a few OEM's disable it but I think I have seen some Acer devices using it before.
The cmd fastboot flashing unlock seems to do something but I suspect it's not a complete cmd
Most bootloaders use
Code:
fastboot flash unlock theunlockcodegivenbytheOEM
followed by
Code:
fastboot oem unlock
then
Code:
fastboot reboot
or just
Code:
fastboot oem unlock
on it's own.
Sometimes none of this is required.
Can you easily recover the device using SPFlashTool (Preferred) or Micro SD and a official update.zip??
If so upload your boot.img LK and preloader (pull them using mtk-su and the dd-backup script in that thread) and I will make a small change to the boot.img and sign it with AVB I will also have a look at the LK and preloader to see if I can see any fastboot cmds you can use mtk-su to flash the modded boot.img if fastboot does not allow flashing.
My simple dd-backup helper script is here see the Readme for instructions. https://github.com/bigrammy/dd-backup-helper-script
Edit FYI See post #12 > for a discussion on this issue in general https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213/page2
Fatsboot Version:
Code:
C:\Minimal ADB and Fastboot>fastboot --version
fastboot version 0.0.1-4500957
Installed as C:\Minimal ADB and Fastboot\fastboot.exe
C:\Minimal ADB and Fastboot>
I don't know if it is possible to flash via SPFlashTool .
I get an Error loading the scatter.txt file.
Micro SD and a official update.zip should be possible i think. But I don't have testet yet. Should I test it before?
dd-backup script shows me this dd-commands:
Code:
acer_asgardfhd:/data/local/tmp # ./dd-backup.sh
##################################################
##################################################
## ##
## dd-backup script ##
## ##
## Generator ##
## ##
## Quick Easy and Universal ##
## ##
## by: xda members @mrmazak @bigrammy ##
## ##
##################################################
##################################################
mkdir: '/sdcard/dd-backup': File exists
1. The dd-backup folder is created!
2. Searching for by-name!
3. Folder located!
4. Begin editing script!
5. Done basic editing
6. Adding dd if cmd's
7. Adding dd of cmd's
8. Getting all the partition names!
9. Joining files!
dd if=/dev/block/platform/soc/11120000.mmc/by-name of=/sdcard/dd-backup/.boot.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/.boot of=/sdcard/dd-backup/flashinfo.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/flashinfo of=/sdcard/dd-backup/userdata.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/userdata of=/sdcard/dd-backup/cache.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/cache of=/sdcard/dd-backup/system.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/system of=/sdcard/dd-backup/metadata.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/metadata of=/sdcard/dd-backup/dkb.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/dkb of=/sdcard/dd-backup/kb.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/kb of=/sdcard/dd-backup/tee2.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/tee2 of=/sdcard/dd-backup/tee1.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/tee1 of=/sdcard/dd-backup/frp.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/frp of=/sdcard/dd-backup/expdb.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/expdb of=/sdcard/dd-backup/logo.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/logo of=/sdcard/dd-backup/para.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/para of=/sdcard/dd-backup/recovery.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/recovery of=/sdcard/dd-backup/lk2.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/lk2 of=/sdcard/dd-backup/lk.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/lk of=/sdcard/dd-backup/seccfg.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/seccfg of=/sdcard/dd-backup/persist.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/persist of=/sdcard/dd-backup/protect2.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/protect2 of=/sdcard/dd-backup/protect1.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/protect1 of=/sdcard/dd-backup/nvram.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/nvram of=/sdcard/dd-backup/proinfo.img
dd if=/dev/block/platform/soc/11120000.mmc/by-name/proinfo of=/sdcard/dd-backup
10. Cleaning up!
11. dd-backup.txt created!
12.!!!! Credits !!!!!
@mrmazak for amazing code skills
@diplomatic for mtk-su!
@bigrammy for my time & effort
@HemanthJabalpuri for helping
@Rortiz2 for all the testing
Hit the above's THANKS Buttons
I think the commands are not right! They are shifted one row!
Where can I find the preloader partition?
Which backups do we need?
Thank you very much.
Hate to necro a year old post but I am interested in permanently rooting my B3-A40 as well, I've made backups of all my files with Wwr and SP flash tool, have tried flashing ported, signed (not entirely sure the signature used, as i used a hovatech tool, any attempts with android kitchen end in the image signing failing and me getting an unsigned_recovery.img), and padded TWRP recovery images, only to have the tablet to say something along the lines of "... CRITICAL: red state... rebooting to system..." when booting into recovery.
Find the stock recovery and boot images attached if anyone is interested. If you need/ want any other files from the backup I'm happy to oblige.
Hello everyone ! XDA is my last hope !
I've hard bricked my asus tab tf300t and i've done every tutorials on XDA and i spent many days to fix it. Every erases commands works except "misc", the RCK freezes and the command stay at erasing 'misc'.... I can't do anything because it freezes at write step. When i want to install from SD CARD, there is no chance to work, nothing happens. Every choices on bootloader menu RCK - ANDROID - WIPE DATA, turns wrong with "unrecoverable bootloader error 0x00000000" message.
You guys, are the last hope i have. Is there something to do to backup my tablet please ? Any command i missed, or tutorial to suggest to me please ? I know it's old but i want to use it and no money to buy a new one.
My bootloader is locked. Only fastboot works.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target didn't report max-download-size
erasing 'system'...
OKAY [ 0.137s]
sending 'system' (800931 KB)...
OKAY [102.980s]
writing 'system'...
_
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d46d9285bf81a
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x000000032a680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.107s
Thanks if someone can helps me.
rabahdu91 said:
I've hard bricked my asus tab tf300t and i've done every tutorials on XDA and i spent many days to fix it.
Click to expand...
Click to collapse
First of all Thanks to @Buster99 and his Solution for fixing this problem,
This guide is for helping you to fix Unrecoverable bootloader error, Hope it will help you out of this problem.
Download “Minimal ADB and Fastboot”. Make a folder C:/Fastboot and extract it there and install it. Download firmware WW_V10.6.1.27.5 from the ASUS official website and unzip it twice. Copy the .blob file from WW_V10.6.1.27.5 into the folder C:/Fastboot. Connect the tablet to PC via USB cable.
Open “Minimal ADB and Fastboot” and put in "fastboot devices"or “adb devices”. The device should appear as "real serial number".
Now type following command-lines in cmd-window step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
fastboot erase user data
fastboot erase boot
fastboot erase misc
fastboot erase cache
After that open C:\put in cmd "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
Good luck!
Hello and thanks for your reply. I've already did it without a success. It seems don't work with locked bootloader. Like I said the erase misc command freezing and don't work.
I think this tablet is good to the trash.
Thanks for your time.
rabahdu91 said:
Hello and thanks for your reply. I've already did it without a success. It seems don't work with locked bootloader. Like I said the erase misc command freezing and don't work.
I think this tablet is good to the trash.
Thanks for your time.
Click to expand...
Click to collapse
You are welcome! Using the thanks button is greatly appreciated.
Please note, as long as you can access the device via fastboot or ADB is always hope to rescue it. Before you really give up have a look at this thread https://forum.xda-developers.com/showthread.php?t=2179759. You will also find an answer for your misc issue.