Related
If you like that I'm doing this, then a thanks is cool, PLEASE DONATE, TIME OR MONEY BUT GIVE SOMETHING TO THESE DEVS!
http://tabletroms.com/forums/showthread.php?356-Honeycomb-on-the-Adam-(Updated)
New - No more partition editing required!
HC16JUN2011
HD Video
-Changelog
Like with any rom, YOU MUST WIPE CACHE, SYSTEM AND DATA, this rom especially, the is a pre alpha and has issues with cache, if you don't clear your info every time you will run into problems. I also clear Dalvik Cache and Battery Stats.
Old info on how to partition
STEP 1 – You need the new NVFlash click here for the unpartitioned onces(may need these)
NVflash edit- pretty simple you need to change the android fastboot full, you'll find that file towards the top of the nvflash folder or you can download my premade ones: (BUT I DIDN'T FORCE YOU TO DOWNLOAD THESE, IF YOU BRICK YOUR DEVICE BY USING THESE THEN YOU BRICKED IT NOT ME, YOU HAVE BEEN WARNED)
Sorry about the mega upload, working on getting my server up, also CWM is untested, it had some problems but I believe that was due to file size.
Clockwork Mod folder
Stock Recovery Folder
The section your looking for looks like this
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=209715200 <---(here is the money)
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=system.img
minus the arrow and the here is the money you'll find the size listed as 209715200, you need to change that to 536870912, once you save go to here to setup your APX drivers and prepare to flash according to the link
STEP 1.1 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY Download Here
Make a copy of your nvflash folder, I name it PIXEL QI CW Mod
STEP 1.2 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY
Thank you darknao
Quick & Dirty method :
Extract the recovery.img from the clockwork.zip, and copy it to the nvflash folder(replace the original one).
Step 2
You need then to put your device into force recovery mode, so turn off your device, then power it on while holding the power + the volume down button till a orange and a yellow lite light up.
Step 3
Run the download.bat file described in the nvflash or unbrick your adam thread - now you can change the file name of the rom to update.zip and flash freely!
Reserved for other usage
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Amon Darthir said:
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Click to expand...
Click to collapse
Gapps are included however this build didn't have them, they had alot of problems with the sync feature, but in theory you should be able to use the latest gingerbread gapps, I will test that right now.
-OK I tested it out, the google setup frooze up on me, after restarting I was able to get into the initial setup, but I have the wifi only model, so I'm going to look into the gapp issue, see if I can find a way around.
-Tried a couple more copies of gapps including a HC edit for the nook sdk HC-- I would press more into this but with the rate of the updates I think its kinda pointless, for now Im going to adb push the market and see what I can get working, hopefully not in-vain since MrGuy and DJSteve move so fast with the updates.
after you use nvflash it will start to boot.. (this would be before flashing update zip) so should I power it down while its booting that first time in order to reboot to recovery and flash the zip?
I do but you don't have to if you use clockwork mod, it doesn't really matter, since you will be building your Dalvik cache once you install your rom.
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
jakobdroid said:
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
Click to expand...
Click to collapse
what operating system do you have? Is your adam in apx mode, and did you edit the android fastboot already? is it still a .bat file
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
jakobdroid said:
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
Click to expand...
Click to collapse
APX is the force recovery, the drivers are included with the NVflash, you must put your device into force recovery, with your device off you press volume down + power till you get your two lights to light up by the power cord, it'll be red and yellow, this is force recovery mode, I am using CW with it and I have listed above how to flash the CW with the increased partition. If you can't figure it out I will be adding the NVflash files with CW mode and non CW mode with the partition edits tonight. I will be turning the change log into a FAQ as well.
Just flashed the ROM and it is awesome. I was just wondering how to get a file managers working. I can't see my sd card. But otherwise, its amazing that honeycomb is up so fast.
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
I'm downloading the file now, working on military lines so its slow to download but that way I can get a better idea of whats going on, also whats your operating system.
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Sounds like you're using linux like me. Are you on ubuntu. Cause I tried and tried and even with chmod and sudo and still got the same error. Consider this post though from: http://notioninkhacks.com/forums/viewtopic.php?f=90&t=1651&start=30
Hey gibson, thanks heaps for that! Actually, yourncomment before asking which folder I was in did it. Very strange, I had to run the commands from 2 folders above the extracted one, then symlink all the other files into the folder I was running from. Will post more later for people who run into similar issues, likely over at the unbricking thread. For now I've got a dualboot setup, and am running a minimal natty rootstock. I tried using the full omap4 image (ubuntu's default arm), but could only get it booting with lots of errors and no gui. Will be aiming to install the netbook desktop (unity 2d) in the next few days.
Re the post above, rayman's boot image already includes the kernel, so it's not needed in the rootstock command. Re the other options, probably will work, but remember rootstock is limited in what you can build... I.e., unless you have heaps of physical ram, you will probably only be able to build a few packages. Head over to xda, and the ubuntu on adam thread there for more info. We have experimented a lot with rootstock builds, and some of that might be useful.
Has anyone tried raymans boot.img with a natty rootstock? Did it work, and has anyone gotten a 2d unity gui up and running? My minimal natty rootstock boots fine, though I notice a few errors. Not sure if they are problematic or not. In any case, the build I made seems to be missing some important wireless tools, so I will likely rebuild it again with them in it soon. Am I likely to run into any problems using rayman's boot image, and steveh's kernel, with a natty build? Happy to post up my work if I get anything decent. Cheers.
osx 10.6.6, thank you!
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Also consider this: http://forum.xda-developers.com/archive/index.php/t-895388.html
Saved me some time thank you...
daiuton said:
Saved me some time thank you...
Click to expand...
Click to collapse
Don't know if the problem is solved yet but that doesn't take away from this honeycomb coolness. So happy to have so much use out of this Adam. Thanks.
that really didnt help, thanks though. i guess i will instal ubuntu in parallels and give it a shot...
Two problems here:
-How can i mount the adam with the computer? To move next updates and update in the next releases
-There is any gapps working (market,etc...)?
Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC
Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).
Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here
Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.
the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.
It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system
If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader
bump? Did anyone end up getting a system image? Thanks.
Nader
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.
ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.
bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.
Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with
I am also not able to flash this system.img file. I get the same error.
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.
I tried to install overcome 8.9 v2.3.1.
but I download the update & not the FULL zip [TEH N00B]
to make things worst I did not backup my system !!!!!!
I can access to the CWM-recovery so im not afraid of my tablet bricked
but the only zip i do have is not complete,
how i can move the the proper file to the tab?
or I need to go the odin route?
in that case what rom should I use?
many thanks
Don't have my tab with me at the moment but doens't the tab show up on a computer if it's in download or recovery mode?
Are you using CWM 5.5.0.4? if yes here is my suggestion...
First you need adb installed on your computer..
Second, you already have overcome full zip file..
This is the step..
Connect your device with computer
From device, Go to recovery - advance menu - mount /system and mount /data
From your computer go to adb terminal and type this
Code:
adb shell "ls /data/media/"
If you can see list of file from your device sdcard, so you make adb work for your device ..
Place your zip file on your path, says on C://overcome.zip and you want to copy the file to /sdcard/download/
This is the code
Code:
Adb push overcome.zip /data/media/download/.
wait for copying progress done..
After you done with moving file to device sdcard check content of your sdcard with this code
Code:
Adb shell "ls /data/media/download/"
When you found your file from list, you can flash overcome.zip from recovery
Thanks for you quick answer
I do have recovery 5.5.0.4
I can get to mount /system & mount/data
when i go to adb and use the command to list the files i got this error
C:\android\sdk-windows\platform-tools>adb shell "ls /data/media/
- exec '/system/bin/sh' failed: No such file or directory (2) -
and tryng to do this command i got this error
C:\android\sdk-windows\platform-tools>adb get-state
unknown
seems like the device is connected
i tried this and the tablet rebooted (not in recovery but reboot)
C:\android\sdk-windows\platform-tools>adb reboot-bootloader
many thanks
Ok I found the way to make that work
i post the reply maybe can help someone else.
suwandiapr should get the credit anyway.
In a phone you have one wrong rom or somenthing and you can get a good one
and copy that to the sd, in a tablet or any device without microsd you need to push the file using this command adb push
let's say you got a rom called supernoob.zip
adb push supernoob.zip /data/media/supernoob.zip
and remeber if you are using a tablet o phone without sd always keep 2 roms in case
Yes i made a simple batch file for windows in development section...
just bought p7310 today and same boot loop actually
hi all
even if i believed i was a geek with nexus or android phones i was wrong !!!!!i just brick my new P7310 wifi tab
-first i root OK
-after i ran rom manager (so manytimes used with my nexus one...) OK
-i flashed CWM but i chose "10.1" (no 8.9 choice at this time) so when rebooting i got this famous (hum) reboot loop just after the welcome screen "samsung galaxy tab 8.9" ..pffffffffff what a stupid beginer i fell about myself ....
- i tried to go in revovery but the loop appears and appaers .....
so i read and read and read forums and probably the solution or a step to a little begining of solution seems to be here ...
i dl Odin v3 and hope to be able to use it and installing a good version ...
thanks to read me and sorry for my english (i m french)
brunobassman said:
hi all
even if i believed i was a geek with nexus or android phones i was wrong !!!!!i just brick my new P7310 wifi tab
-first i root OK
-after i ran rom manager (so manytimes used with my nexus one...) OK
-i flashed CWM but i chose "10.1" (no 8.9 choice at this time) so when rebooting i got this famous (hum) reboot loop just after the welcome screen "samsung galaxy tab 8.9" ..pffffffffff what a stupid beginer i fell about myself ....
- i tried to go in revovery but the loop appears and appaers .....
so i read and read and read forums and probably the solution or a step to a little begining of solution seems to be here ...
i dl Odin v3 and hope to be able to use it and installing a good version ...
thanks to read me and sorry for my english (i m french)
Click to expand...
Click to collapse
Go to dowload menu and try to flash stock recovery in your tab..
Here is the stock recovery for p7300/p7310
Start odin, and put the file in pda slot..
Please see entire thread for your own safety..
[My i9305 is not connecting with PC, I tried *#7284# (UART & USB > PDA), but it didn't work...
so I have to find the following way to root my device & to install custom ROMs... It worked perfectly...
But I still want to connect my phone to PC through USB, any help will be appreciated. Thanks]
First, download and install 'Framaroot.apk'. It is available at http://forum.xda-developers.com/showthread.php?t=2130276
Now, open the app and tap on 'Aragorn'. And your device is rooted .
It you want to use custom ROMs, you need custom recovery. So,
Install 'Terminal Emulator.apk' form Play Strore.
Download any TWRP/CWM recovery image for i9305 (.img file). [For TWRP images: http://techerrata.com/browse/twrp2/i9305]
Place it on your internal storage (on root directory).
Rename the .img file to 'recovery.img'
Now, open 'Terminal Emulator' and type following commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p9
or, You can use 'Mobile Odin' / 'Recovery Tools - Flasher' [available in Google Play] to flash .tar recoveries.
You are DONE .
I think it is more advisable to flash recovery using an Application rather than the command line, since one digit here and there, you have a bricked phone.
I would suggest use an app like this after rooting the phone
mtatohin said:
[My i9305 is not connecting with PC, I tried *#7284# (UART & USB > PDA), but it didn't work...
so I have to find the following way to root my device & to install custom ROMs... It worked perfectly...
But I still want to connect my phone to PC through USB, any help will be appreciated. Thanks]
First, download and install 'Framaroot.apk'. It is available at http://forum.xda-developers.com/showthread.php?t=2130276
Now, open the app and tap on 'Aragorn'. And your device is rooted .
It you want to use custom ROMs, you need custom recovery. So,
Install 'Terminal Emulator.apk' form Play Strore.
Download any TWRP/CWM recovery image for i9305 (.img file). [For TWRP images: http://techerrata.com/browse/twrp2/i9305]
Place it on your internal storage (on root directory).
Rename the .img file to 'recovery.img'
Now, open 'Terminal Emulator' and type following commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p9
You are DONE .
Click to expand...
Click to collapse
Framaroot did not work for my GT-I9305. It says 'Error #6' . Are they different from each other? Exynos? I am in UK using international edition.
after rooting using framaroot I flashed costum recovery.IMG using mobile Odin. that is safer
@ enarsee: Yeah, you can use 'Mobile Odin' too. Thanks for your suggestion.
@ shayind4: I'm getting the same error on 4.3 ROM! I think you have to try something else. You can try this http://forum.xda-developers.com/showthread.php?t=2352669
@ reymasters: Yes, you can use it. Its safe and easy. I will edit my post.
98926828
This method doesn't work with my GT-I9305 also. I'm so sorry I flashed 4.3 with odin...
elektronchika said:
This method doesn't work with my GT-I9305 also. I'm so sorry I flashed 4.3 with odin...
Click to expand...
Click to collapse
This method works upto 4.1.2
Hello, a few days ago my zenfone started acting up (again), with built in applications crashing randomly and failing to boot half of the times. I always managed to fix it downloading the firmware from Asus' website and re-upgrate it, but this time it didn't worked out quite well. It now refuses to boot (sometimes gets stucked at boot, simetimes I manage to have asus screen). Booting into recovery prints `E:mount fail, change path to mount /dev/block/mmcblk1`, then errors about cache partiton not being found.
I've tried pretty much anything that would not result in data loss:
Wiping cache doesn't report errors, but doesn't help either,
Flashing stock boot.img and droidboot.img don't report error, but doesn't help either,
Flashing TWRP to recovery reports success, but I still get stock recovery,
Sideload fails coz it doesn't find expected mounts
Adb shell doesn't work as it can't find `/system/bin/whatever`
`adb pull /proc/partitions` returns what looks like a legit partitions list for mmcblk0 to me
Does anyone know what else I can try to rescue the data on the phone?
WobLight said:
Hello, a few days ago my zenfone started acting up (again), with built in applications crashing randomly and failing to boot half of the times. I always managed to fix it downloading the firmware from Asus' website and re-upgrate it, but this time it didn't worked out quite well. It now refuses to boot (sometimes gets stucked at boot, simetimes I manage to have asus screen). Booting into recovery prints `E:mount fail, change path to mount /dev/block/mmcblk1`, then errors about cache partiton not being found.
I've tried pretty much anything that would not result in data loss:
Wiping cache doesn't report errors, but doesn't help either,
Flashing stock boot.img and droidboot.img don't report error, but doesn't help either,
Flashing TWRP to recovery reports success, but I still get stock recovery,
Sideload fails coz it doesn't find expected mounts
Adb shell doesn't work as it can't find `/system/bin/whatever`
`adb pull /proc/partitions` returns what looks like a legit partitions list for mmcblk0 to me
Does anyone know what else I can try to rescue the data on the phone?
Click to expand...
Click to collapse
When you flash TWRP and try to boot into recovery, have you tried using adb with "adb reboot" command?
Have you tried the "fastboot boot twrp.img" command"(with the TWRP file renamed to "twrp.img")? If you can get that to work, you can temporarily boot a TWRP session and then use it to make a nandroid backup.
Have you tried creating an adb backup, as described in the link below?
https://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
If you have corrupted partitions, you might not retrive anything, you might have no choice but to use an option that wipes, repartitions and flashes the device.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When you flash TWRP and try to boot into recovery, have you tried using adb with "adb reboot" command?
Have you tried the "fastboot boot twrp.img" command"(with the TWRP file renamed to "twrp.img")? If you can get that to work, you can temporarily boot a TWRP session and then use it to make a nandroid backup.
Have you tried creating an adb backup, as described in the link below?
https://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
If you have corrupted partitions, you might not retrive anything, you might have no choice but to use an option that wipes, repartitions and flashes the device.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thanks for suggestions,
adb backup doesn't work. It complains about /system/bin/sh not found (looks like either the partition isn't mounted or the failed update erased it).
fastboot boot doesn't work. I was messing with boot.img before, and I found out that intel's boot.img (my zenfone is x86) is not standard format. fastboot logs `creating boot image...`, I suspect it doesn't work at all for intel's. It reports 'booting OK' but the phone doesn't reboot at all.
fastboot flash recovery twrp.img returns OK but still stock recovery...
WobLight said:
thanks for suggestions,
adb backup doesn't work. It complains about /system/bin/sh not found (looks like either the partition isn't mounted or the failed update erased it).
fastboot boot doesn't work. I was messing with boot.img before, and I found out that intel's boot.img (my zenfone is x86) is not standard format. fastboot logs `creating boot image...`, I suspect it doesn't work at all for intel's. It reports 'booting OK' but the phone doesn't reboot at all.
fastboot flash recovery twrp.img returns OK but still stock recovery...
Click to expand...
Click to collapse
I have an intel atom tablet that I used this tool to boot TWRP then root and create nandroid backups with.
https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
There may be similar tools for your intel tablet, or maybe you can modify this tool or work out something similar.
There is another similar tool that I used on an intel based RCA Viking III tablet.
Sent from my LGL84VL using Tapatalk
Droidriven said:
I have an intel atom tablet that I used this tool to boot TWRP then root and create nandroid backups with.
https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
There may be similar tools for your intel tablet, or maybe you can modify this tool or work out something similar.
There is another similar tool that I used on an intel based RCA Viking III tablet.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
It worked!!! :victory:
Thank you so much for helping me out with this, I spent over a week trying to fix/backup data, I was going to give up.
After backing up things properly I'll play with it, see if I can have it booting again (maybe not stock system ).
WobLight said:
It worked!!! :victory:
Thank you so much for helping me out with this, I spent over a week trying to fix/backup data, I was going to give up.
After backing up things properly I'll play with it, see if I can have it booting again (maybe not stock system ).
Click to expand...
Click to collapse
Be careful, this tool is built to work on a lot of different devices with different hardware and different partitioning, the differences in partitions means that it cannot create or restore nandroid backups on all devices that the tool can boot on. Some intel devices that this tool works on can create and restore nandroid backups, some can't, it just depends on how the device is partitioned. It can also be used to flash ROMs on some devices but not on others.
This tool can boot a temporary recovery session on a lot of devices but not all of them can use all of the features in the recovery that it boots.
This difference in partitioning means that trying to restore a backup or flash a ROM can break some devices because the partitioning isn't right. So just be warned, you will be exposing your device to a certain amount of risk if you try using all of the features in the temporary recovery session.
Also, this tool was designed to boot a temporary recovery session on intel devices that have a locked bootloader, this recovery session can not flash ROMs on intel devices that have a locked bootloader, it can only be used to flash devices that have an unlocked bootloader. If your bootloader is locked, you'll brick your device if you attempt flashing a ROM on your device using this recovery session.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Be careful, this tool is built to work on a lot of different devices with different hardware and different partitioning, the differences in partitions means that it cannot create or restore nandroid backups on all devices that the tool can boot on. Some intel devices that this tool works on can create and restore nandroid backups, some can't, it just depends on how the device is partitioned. It can also be used to flash ROMs on some devices but not on others.
This tool can boot a temporary recovery session on a lot of devices but not all of them can use all of the features in the recovery that it boots.
This difference in partitioning means that trying to restore a backup or flash a ROM can break some devices because the partitioning isn't right. So just be warned, you will be exposing your device to a certain amount of risk if you try using all of the features in the temporary recovery session.
Also, this tool was designed to boot a temporary recovery session on intel devices that have a locked bootloader, this recovery session can not flash ROMs on intel devices that have a locked bootloader, it can only be used to flash devices that have an unlocked bootloader. If your bootloader is locked, you'll brick your device if you attempt flashing a ROM on your device using this recovery session.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank for your concern, I've backed up contents of the sdcard and data partition (other partitions fails to mount) to an external SD. Ofc sdcard contents are just copy/pasted, as for data partition I've checked and looks like I can open the twrp archives from linux. I'm gonna try to clone the whole mmcblk0 before trying anything weird tho .
WobLight said:
Thank for your concern, I've backed up contents of the sdcard and data partition (other partitions fails to mount) to an external SD. Ofc sdcard contents are just copy/pasted, as for data partition I've checked and looks like I can open the twrp archives from linux. I'm gonna try to clone the whole mmcblk0 before trying anything weird tho .
Click to expand...
Click to collapse
You might can modify the tool itself or the TWRP .img that is built into the tool to modify it to work with the way that your device is partitioned, that way it mounts, reads and writes those partitions correctly.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You might can modify the tool itself or the TWRP .img that is built into the tool to modify it to work with the way that your device is partitioned, that way it mounts, reads and writes those partitions correctly.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I've tried to use the twrp for z00d I have previously downloaded, I have to do some tweaking to make it boot. Even tho it looks like a newer version, console is crashing and partitions won't work anyway. Since stock recovery fails to mount cache I guess there's corruption somewhere on the device. I might have found the stock partitions.tbl, but if I manage to clone mmcblk0 to an external sd, I can perhaps mess with the image with linux and confirm whether is there's corruption.
WobLight said:
I've tried to use the twrp for z00d I have previously downloaded, I have to do some tweaking to make it boot. Even tho it looks like a newer version, console is crashing and partitions won't work anyway. Since stock recovery fails to mount cache I guess there's corruption somewhere on the device. I might have found the stock partitions.tbl, but if I manage to clone mmcblk0 to an external sd, I can perhaps mess with the image with linux and confirm whether is there's corruption.
Click to expand...
Click to collapse
Here is another tool that I used on an intel based RCA tablet, it might can be adapted to be used on your device if you know or can find out where the tool can be modified to work on your device.
https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Sent from my LGL84VL using Tapatalk
Droidriven said:
Here is another tool that I used on an intel based RCA tablet, it might can be adapted to be used on your device if you know or can find out where the tool can be modified to work on your device.
https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hello, I've tried a few more stuff today, by the looks of it, the device silently fails to write anything.
I've tried to use adb push to flash a fixed image to /dev/block/mmcblk0, tried fastboot flash, tried dd from the recovery, even tho it reports ok, nothing is actually written on the device. I've tried to rename a file in data (which does mount), but after unmounting/remounting the partition the file still have the old name.
Maybe I can try loading a system on the external sd instead, but that's it.
Thanks again for your help, I was able to recover the data which was actually my priority.
EDIT: partition command also fails