Related
I have mine rooted, there is something very interesting about the way Samsung did this. This phone has like 20 different partitionssee below, however I think I know how the phone is able to restore root and the recovery after boot. These 20 partitions include copies of each other. For example if you do su on terminal emulator and then you type "cat /proc/partitions" it will list all the partitions. Notice how some partitions have different labels but are the same size. These are the respective back ups(i think). The only partition that I know is "stl9" or "st9" is the system.
I tried flash_image recovery and said it wasn't a recognized partition as the BH2 also does not have mtd. cat /proc/mtd produces nothing. Hope this helps.
Oh 1 last thing it seems I may have found an exploit with the device management.apk. It has the option to run a bootloader/bootstrap test, could this be exploited to install customer recovery? Its just a thought...
Can someone with root, compile busybox for install on the Behold 2. I am sorry I only have Windows 7.
Terminal Output:
See the areas highlighted in BOLD. The G1 has half the number of partitions and mtd has output.
$ export PATH=/data/local/bin:$PATH
$ su
# cat proc/partitions
major minor #blocks name
137 0 513024 bml0/c
137 1 2048 bml1
137 2 512 bml2
137 3 512 bml3
137 4 1024 bml4
137 5 23040 bml5
137 6 6144 bml6
137 7 23040 bml7
137 8 6144 bml8
137 9 226304 bml9
137 10 8192 bml10
137 11 512 bml11
137 12 40960 bml12
137 13 1024 bml13
137 14 173568 bml14
138 9 210432 stl9
138 12 25088 stl12
138 14 157696 stl14
179 0 1982464 mmcblk0
179 1 1982338 mmcblk0p1
#
Click to expand...
Click to collapse
Samsung is doing their best to screw us here aren't they?
I have an ubuntu partition, but it will be a bit before I can compile. I'm writing up guides to overhaul the current UI.
having trouble with adb in ubuntu. I'll retry tomorrow, but this could take a while. Probably best for someone else to take this one on.
What's the output for 'mount'?
I posted this on alldroid.org today ,,, samsung seem to have used some of its bada OS and or UI in the behold 2 ,.,,.,. I was wondering if someone could download their SDK and see what they can find out ,.,,., maybe it could help us with ROOT .,.,....,.,
SDK link http://developer.bada.com/apis/docs/commonpage.do?menu=MC01040000&mtb1=&mtb2=
''Re: Important Behold 2 Discovery / 1st step to Custom Roms
They are similar but for that method you need 'new PcStudio', which does not recognize the behold 2,.,..,.,.,
BTW the galaxy (( samsung i7500 )) is almost the same as the behold 2 ,,,, same hardware but the behold 2 has a lot more memory ,.,,..
http://androidforums.com/samsung-i7500/ ... rom-s.html
one interesting thing i did find this weekend while doing some research was that (I think ) samsung has implemented some of its BADA Os on the behold 2 look at the video and let me know what you think
http://www.gsmarena.com/samsung_finally ... s-1311.php ''''
PS:;: (thanks to yatimameiji) this was just found and hopefully it can help you look in the right place '''''To get the recovery menu ,.,,.,. when you do vol. down+call button+power and the triangle comes up .,. then do home + power ., recovery menu,''''''' I got it up but cant select anything and there's the e:can;t open cache and some others
Finally some posts back. I thought no one was going to respond and I was going to delete this thread. So this is great news that we can now enter recovery mode. Also I know whats plauging the device with the battery issue. It seems the phone is reading the battery as 1440 mah and the battery is tagged 1500mah. This can be confirmed by using BetterCut and adding the shortcut Battery read.
dan0zone said:
I posted this on alldroid.org today ,,, samsung seem to have used some of its bada OS and or UI in the behold 2 ,.,,.,. I was wondering if someone could download their SDK and see what they can find out ,.,,., maybe it could help us with ROOT .,.,....,.,
SDK link http://developer.bada.com/apis/docs/commonpage.do?menu=MC01040000&mtb1=&mtb2=
Click to expand...
Click to collapse
It seems so close to the Android Developer Site. Did AOSP give some code to Samsung as a base?
I believe so ,I remember reading that it was going to be like the OPhone project , but samsung wants to use this like they use touchwiz on all their touch screen phones ,.,..,.,
ok so i was playing around with my samsung behold2 today, all i found was recovery mode (voldown+call+power) and fastboot (dpadleft+power). im currently installing the android sdk as we speak, after that will play around with this a bit more.
We had a good look at this over at androidforums (behold and galaxy sub forums).
It seems they are using some secure bootloader, and those other partitions (which almost corespond in size) seem to be the original partition in a security container.
I had assumed that on boot if the main partition is modified it would simply reflash it. However we have now been able to 'persistant root' the phone. (check in the behold section on androidforums). We hijack the playlogo file, and insert the shell commands to execute the exploit executable on every boot. This happens after init.rc so making custom roms is going to be a bit of a headache.
Whats strange tho is why it doesnt recognise the system partition was changed when we mod playlogo. Perhaps it just wipes the bin and xbin directories and reextracts them. That would make life alot easier.
I was going to sell my galaxy and switch to a behold, but I couldnt find one cheap enough. So i've stopped looking at all this now.
Hope that helps anyway.
well we have made some head way ..,,.,., we can now flash between builds for the behold2 via ODIN_flasher . For now we have two builds an older build and the one shipped with the phone .,.,.,. so what i think we need is a way to edit the .tar files within the flasher but keep the partition structure that samsung has in_place .,,,. What i have notice is that if you connect to ddms , and go to the system info tab or allocation tracker , you will see that samsung has renamed every thing as a kernel, even the browser .,.,., if we get our hands on sammy's build environment maybe we can make sense of their madness,.,.,..
Odin isnt actually anything new. We've been using it with the galaxy for a while now.
The phones' bootloader contains a download mode, which also forwards to the AMSS's OEMBL in download mode. Odin simply forwards the files to this bootloader without doing anything clever. This is why you can take ANY update from NPS and apply it using odin as is.
We have tried flashing galaxy partitions onto the behold, but as i said in an earlier post there is a secure bootloader and it simply rejects the images.
I havnt downloaded this H6 leaked behold image, but it probably just contains yafs images, probably in a security container. You could unyaffs them, modify and yaffs them up again. Just modifying them is trivial. I'm pretty sure that the bootloader will just reject any modified images tho. Sorry but I don't think this is going to get you anywhere.
On a security unlocked phone like the galaxy we just edit the system or recovery images and flash them back using Odin. Similarly fastboot can also do it. On the behold however i'm pretty sure it wont accept anything that isnt signed.
The only interesting thing to try would be to try to flash the galaxy bootloader onto the behold using odin. We have both the arm9 and arm11 bootloaders if you'd like to try. This is VERY VERY VERY risky and in all likelyhood will brick your phone. But if it works you should be able to manage partitions simply like with the galaxy.
The very first thing you guys should look at is to compare the system image of the galaxy and the behold. Check if there is a security container around the behold one or not. If there is, attempt to exploit it (change length fields, change offsets, create oversized image - the usual stuff).
I think there are only 2 routes to acheive what you want:
- quick route
Use a userland exploit, like the current root. Then use the persisitant root idea to run a script which modified your filesystem on boot - possibly extracting a custom rom from the sdcard onto the system partition.
- Slow route
Try to find a flaw in the secure bootloader, or some other exploit to allow you to flash a modified bootloader.
You're idea of just editing the firmware files directly is really unlikely to work.
Thanks for your input Kam ..well it just a thought , I knew the signing would of been the issue ( same as with the G1 roms and themes ) .,.,., I know someone will figure it out .,.,.. I would love to help with getting this going , but I work 14 hour days ,., I should get a second behold2 soon so I can use one for testing ,,, well till i brick it .........
I'm gonna browse some of the galaxy forums to see how they doing it ,., I """think""" the galaxy is closer to stock android than the behold2 is .,.
BTW , H6 image you talking about , is that one posted by sammydroid ? because he also has a J6 image , H6 is older .
Yeah thats the one. I have a galaxy, and not a behold so my interest in this is kinda limited. I only really got into it because i was going to switch to the behold.
Personally I think you guys are better off just using the persistant root to modify the OS after boot for now.
Samsung Source Code
Does this help at all?
http://opensource.samsungmobile.com/download/OpenSource/SGH-T939_OpenSource.zip
Appears to be the build source for the existing rom. Don't have access to a *nix box to dig into it right now...
Here's the tutorial to install busybox for behold 2.
http://www.myhangoutonline.com/2010/01/08/install-busybox-on-behold-ii/
kam187 said:
Odin isnt actually anything new. We've been using it with the galaxy for a while now.
The phones' bootloader contains a download mode, which also forwards to the AMSS's OEMBL in download mode. Odin simply forwards the files to this bootloader without doing anything clever. This is why you can take ANY update from NPS and apply it using odin as is.
We have tried flashing galaxy partitions onto the behold, but as i said in an earlier post there is a secure bootloader and it simply rejects the images.
I havnt downloaded this H6 leaked behold image, but it probably just contains yafs images, probably in a security container. You could unyaffs them, modify and yaffs them up again. Just modifying them is trivial. I'm pretty sure that the bootloader will just reject any modified images tho. Sorry but I don't think this is going to get you anywhere.
On a security unlocked phone like the galaxy we just edit the system or recovery images and flash them back using Odin. Similarly fastboot can also do it. On the behold however i'm pretty sure it wont accept anything that isnt signed.
The only interesting thing to try would be to try to flash the galaxy bootloader onto the behold using odin. We have both the arm9 and arm11 bootloaders if you'd like to try. This is VERY VERY VERY risky and in all likelyhood will brick your phone. But if it works you should be able to manage partitions simply like with the galaxy.
The very first thing you guys should look at is to compare the system image of the galaxy and the behold. Check if there is a security container around the behold one or not. If there is, attempt to exploit it (change length fields, change offsets, create oversized image - the usual stuff).
I think there are only 2 routes to acheive what you want:
- quick route
Use a userland exploit, like the current root. Then use the persisitant root idea to run a script which modified your filesystem on boot - possibly extracting a custom rom from the sdcard onto the system partition.
- Slow route
Try to find a flaw in the secure bootloader, or some other exploit to allow you to flash a modified bootloader.
You're idea of just editing the firmware files directly is really unlikely to work.
Click to expand...
Click to collapse
Have a second unit on hand now (for about a week) so bricking isn't a concern and can/will try these options... but need guidance. can jump on irc for assistance... anyone interested? The above seems totally possible.... but out of my league without help.
Thanks to MobileBand we had some succees Managed to get the galaxy system onto the behold. Force close problem at the moment but stay tuned.
PS. its fastttttttttttttttttttt
Let me publicly state that kam187 ROCKS! Kudos on the work last night!
Behold owners; start getting hyped... this is the break we've been looking for!
love the work
love you guys work man i have 140mb free on my behold 2 thats with out task manager its blazin fast but always wanted to do something differnent with it can you pleaseeeeeeeeeeee lol ( : ) : post a rom and turt
I think I finally have a valid post worth of this forum.
It looks like the traditional Recovery images I found on the threads here are looking for:
/dev/block/mmcblk1p3
But when I look in my Xoom via adb shell (unrooted mind you) all I see in /dev/block is 0p1-10:
mmcblk0
mmcblk0p1
mmcblk0p2
mmcblk0p3
...
mmcblk0p10
There is nothing beyond blk0p10, no blk1, etc..
This is a Xoom 3G tab which got the 4G LTE upgrade recently from Motorola. They also unrooted my Xoom before they shipped it back. Might of even upgraded it, I don't know. How nice of them.
So now I am trying to re-root it and CWM fails to load the /mnt/sdcard or otherwise Internal Storage for me to choose a zip.
Any ideas?? Can anyone make me a custom Recovery which has these tweaks to see if it gets past this or still has more issues?
Thanks in advance!
Anyone have any ideas? Thanks!
*bump* Anyone have any clue? I resurrected my Xoom today to load the ICS Stingray ROM, only to run into this same loop again.. #FAIL
I've been following this thread very carefully: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
I am stuck on the memory block address. Does anyone know which block is the entire 32GB block for Samsung Note 3? I tried mmcblk0p12 which does nothing and I tried mmcblk0p15 which only downloaded 13mb in a few seconds. I need the address that downloads all 32gb!
please help!
curtisbouvier said:
I've been following this thread very carefully: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
I am stuck on the memory block address. Does anyone know which block is the entire 32GB block for Samsung Note 3? I tried mmcblk0p12 which does nothing and I tried mmcblk0p15 which only downloaded 13mb in a few seconds. I need the address that downloads all 32gb!
please help!
Click to expand...
Click to collapse
Try to look for a larger size. But as far as i know, the mmcblk0p12 is the correct file.
You can use deleted videos from Note 3 phone with samsung data recovery software, see this guide that helped me before: samsung galaxy data recovery
It is easy to follow and works well for me.
Hi all,
I had an idea last night; our Android phones are computers, right? And recently someone found a way to run Android apps on Linux.
Many developers here are familiar with Arch Linux; many are also familiar with its minimalist approach. There is a way to install Arch Linux ARM for rooted phones to be used inside Android, but what if we made it better -- what if we made an Android ROM based off Arch that you built from scratch? Consider the possibilities: If you don't care to use your phone (maybe it's outdated) as a regular phone, make it into a computer. Hook it up to a monitor (Chromecast, anyone?) and perform normal computing operations. Although the Moto G lacks RAM, running it with just a WM and making swapspace would do wonders; a Moto X would be even more perfect. Why not re-purpose your old phones into new computers?
I have been using Arch as my primary OS (only one installed on this computer) for 5 or 6 months now, and while I'm no expert I think that getting this to work wouldn't be terribly difficult. My thought on how this project would proceed:
1) Install a basic system (or boot some sort of install img) from fastboot
2) Repartition the internal SD card, do away with Android (maybe add dual-boot support eventually?)
3) Install Arch normally
4) Work on a package for a DE that supports touch screen
5) Create an easy package to allow for installation of Play store and running apps
The beauty of this would be similar to Arch: flexibility, choice and the option to run a minimalist version of Android, stripping away excess features so that users can have what THEY need.
I'm going to try to turn the ISO into an IMG and see if fastboot will let me boot it. I'll report back; if anyone can help out, let me know -- can't do it all by myself! I'd love any recommendations you guys have, or if it won't work just let me know right off the bat lol. Thanks!
EDIT: Tried making an img but don't think fastboot can boot such large images... maybe a custom recovery that can boot images? Basically I'm just trying to figure out how to unmount the partitions and modify them. Obviously if you can't it will be a bit harder because we'll have to build an Arch system that fits into the Android partitions. But a single root partition would probably be most convenient for these purposes.
Repartitioning the internal storage is extremely risky and you could hard-brick your phone
Good luck anyway, you might wanna look into Ubuntu Touch
DustArma said:
Repartitioning the internal storage is extremely risky and you could hard-brick your phone
Good luck anyway, you might wanna look into Ubuntu Touch
Click to expand...
Click to collapse
So I've read... and yes yes, there's Ubuntu Touch, but Arch deserves a mobile port too!
Sounds good... Can I help you with this project?
P.S. I'm not a developer
Sent from my XT1033 using XDA Free mobile app
K3VYNC said:
Sounds good... Can I help you with this project?
P.S. I'm not a developer
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
Certainly!
From elinux.org: Fastboot is the name of a tool used to manipulate the flash partitions of the Android developer phone. It can also boot the phone using a kernel image or root filesystem image which reside on the host machine rather than in the phone flash. Think fastboot is what we need. @DustArma mentioned that it's risky to change partitions, but can that hurt fastboot? Can you make a backup of the partitions with fastboot?
This is extremely risky and I don't really think you should attempt it unless you've got more than 3 devices just waiting to get bricked before you may achieve something. I'm not trying to disrespect at all, but a project like this takes a lot of skill and more than just basic knowledge on how to build. Of course, I'm not exactly trying to stop anyone from doing this, but it is extremely risky for your device.
What you are suggesting is very, very difficult to achieve and as it's been said, it requieres a deep knowledge and expertise just to give it a shot... and if I had to bet I'd say it would fail even in the most expert hands. Respectfully said... it sounds like you are considering it out of the lack of experience and skill. Talk to kernel and rom devs, falcon has tricky hardware.
Just my opinion, for sure you are free to do whatever you want with your device.
Oh wow, really? I thought that fastboot was like BIOS, so messing with internal storage would be nothing. Who would you recommend I talk to @fermasia?
Sent from my Moto G using XDA Free mobile app
Jhdoubleoseven said:
Oh wow, really? I thought that fastboot was like BIOS, so messing with internal storage would be nothing. Who would you recommend I talk to @fermasia?
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
YoshiShaPow has done great with his kernel and you read his opinion... But you can browse around the forum. [emoji106]
So what makes Android phones unique compared to computers... Like I can remove my hard drive and my computer can still function, assuming I can boot from a USB drive or CD
Sent from my Moto G using XDA Free mobile app
first of all, wrong section as nothing is uploaded yet and you are just in discussion phase.
second you might get lucky with multiom support. should be less risky. but i don't know how pure arch will run considering so much closed source binary blobs for arm system.
should be a fun project. you should not get discouraged by what others say and you can always get your mobile repaired.
Well...haters gonna hate. No offense. But I think your idea is great!
I think here's what our first thing should be:
1. Since archlinux has a different partition table, we need to study and analyze both android(specifically moto g's) and Arch Linux partition table.
2. A new(or a modified) partition table will have to made, which has the following:
a)keeps fastboot partition untouched(so that we are "brick-free")
b)matches the partition sizes of Arch Linux keeping in mind the internal storage limitation. (Theoretically, bootable USB should be a safer and an easier option).
3. This partition can then be flashed using fastboot (same as gpt.bin file in firmware packages. GPT-General Partition Table).
This completes the first important step. Next step will be the kernel that supports our phones hardware.
PS: I am not a developer. I possess basic knowledge of linux. One can expect nice ideas from me. I'll help in whatever way I can.
Sent from my Moto G using Tapatalk
Please leave the development section for actual development
Thread moved
So I was looking at this:
https://wiki.ubuntu.com/Touch/ContainerArchitecture
And it tells us all about how Ubuntu Touch does it -- think ArchROM needs to be engineered in much the same way, possibly using Ubuntu Touch as a base then slowly removing it and replacing it with Arch -- as they did to Android. Not pure but it works.
Code:
Number Start (sector) End (sector) Size Code Name
1 256 131327 64.0M 0700 modem
2 131328 132351 512K 0700 sbl1
3 132352 132415 32768 0700 DDR
4 132608 133631 512K 0700 aboot
5 135608 136007 200K 0700 rpm
6 136608 137407 400K 0700 tz
7 137608 137671 32768 0700 sdi
8 137672 138695 512K 0700 utags
9 138696 142791 2048K 0700 logs
10 142792 147455 2332K 0700 padA
11 147456 148479 512K 0700 abootBackup
12 150456 150855 200K 0700 rpmBackup
13 151456 152255 400K 0700 tzBackup
14 152456 152519 32768 0700 sdiBackup
15 152520 153543 512K 0700 utagsBackup
16 153544 155647 1052K 0700 padB
17 155648 158719 1536K 0700 modemst1
18 158720 161791 1536K 0700 modemst2
19 161792 162815 512K 0700 hob
20 162816 162831 8192 0700 dhob
21 163072 166143 1536K 0700 fsg
22 166144 166145 1024 0700 fsc
23 166146 166161 8192 0700 ssd
24 166162 168209 1024K 0700 sp
25 168210 168465 128K 0700 cid
26 168466 174609 3072K 0700 pds
27 174610 182801 4096K 0700 logo
28 182802 190993 4096K 0700 clogo
29 191232 207615 8192K 0700 persist
30 207616 208639 512K 0700 misc
31 208640 229119 10.0M 0700 boot
32 229120 249599 10.0M 0700 recovery
33 249600 1605631 662M 0700 cache
34 1605632 3604479 976M 0700 system
35 3604480 3620863 8192K 0700 kpan
36 3620864 30711551 12.9G 0700 userdata
There is what I found for the partitions. Obviously, as mentioned in the Ubuntu Touch article, it would be MUCH easier to let Android initialize the hw then boot up the Arch rfs
Look at this.
https://plus.google.com/101741693669616771532/posts/WZtnchkubYf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I was trying to install a custom recovery for my tablet, but I did the stupidest thing -- I'll try to explain everything that I did. So first, I downloaded the custom recovery from this thread: http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094 and the file name was: sm-t330nu-Philz-6_58_9-milletwifiue-recovery.zip -- Then, I used terminal emulator on my tablet to flash the custom recovery image. Here is what I put:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
reboot recovery
It told me this:
write error: no space left on device
So I searched google for a way to get around this problem. I found something, and I was stupid enough to put in this into the terminal emulator:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p3
bs=1 seek=0
reboot recovery
I put this in without knowing what would happen *facepalm* So when my device rebooted, it was just a black screen. I tried connecting it to my computer. When I did, I saw a driver was trying to install. The computer told me that no driver was found. The name of the driver is "QHSUSB_BULK" I downloaded the samsung usb drivers but that didn't work. The driver "QHSUSB_BULK" has a yellow exclamation mark on it. I also tried connecting the tablet to my charger, but the screen was still black. I even tried holding the power button and volume up button, but still nothing. I don't know what to do anymore. If someone know of a way to fix this, please tell me. I really need help right now. I'm in desperate need for a fix. Thank you all in advance.
sdkfreak123 said:
So I was trying to install a custom recovery for my tablet, but I did the stupidest thing -- I'll try to explain everything that I did. So first, I downloaded the custom recovery from this thread: http://forum.xda-developers.com/tab-4/development/recovery-philz-smnu-t2980094 and the file name was: sm-t330nu-Philz-6_58_9-milletwifiue-recovery.zip -- Then, I used terminal emulator on my tablet to flash the custom recovery image. /QUOTE]
You should have flashed it with odin. Try pressing and holding power+volume up and down+Home buttons all at the same time for a minute or so and see if it does something.
Click to expand...
Click to collapse
hey guys,
some points to make,
1 Use the XDA search function and reasearch the PROPER way to do what it is you want to do.
2 You DO NOT flash a ZIP file in odin. You flash a TAR or TAR.MD5 image in odin.
3 To @sdkfreak123, not meaning to sound harsh jerk-facey but,
WHY FOR THE LOVE OF FRENCH TOAST WITH SPRINKLES WOULD
YOU WRITE A RECOVERY IMAGE TO MMCBLK0P13 ON A GALAXY TAB SM-T330NU !?!?!?!
Reading the entire recovery thread and or making a request either in the thread or via pm is the way to go.
Don't misunderstand me, i feel your pain, but your tab is most likely done.
This is the partition layout of the sm-t330nu, the areas you overwrote are in RED
Code:
Number Start End Size File system Name Flags
1 4194kB 18.9MB 14.7MB apnhlos
2 18.9MB 71.0MB 52.2MB modem
[COLOR="Red"]3 71.0MB 71.6MB 524kB sbl1[/COLOR] ----> FATALITY
4 71.6MB 71.6MB 32.8kB dbi
5 71.6MB 71.6MB 32.8kB ddr
6 71.6MB 73.7MB 2097kB aboot
7 73.7MB 74.3MB 524kB rpm
8 74.3MB 74.8MB 524kB tz
9 74.8MB 75.8MB 1049kB pad
10 75.8MB 86.3MB 10.5MB param
11 86.3MB 101MB 14.7MB ext4 efs
12 101MB 104MB 3146kB modemst1
[COLOR="Red"]13 104MB 107MB 3146kB modemst2[/COLOR]
14 107MB 118MB 10.5MB boot
[COLOR="SeaGreen"]15 118MB 128MB 10.5MB recovery[/COLOR] ----> THIS IS YOUR RECOVERY BLOCK
16 128MB 139MB 10.5MB fota
17 139MB 146MB 7331kB backup
18 146MB 149MB 3146kB fsg
19 149MB 149MB 1024B fsc
20 149MB 149MB 8192B ssd
21 149MB 158MB 8389kB ext4 persist
22 158MB 167MB 9437kB ext4 persdata
23 167MB 2579MB 2412MB ext4 system
24 2579MB 2893MB 315MB ext4 cache
25 2893MB 2914MB 21.0MB ext4 hidden
26 2914MB 15.8GB 12.8GB ext4 userdata
You should be using Odin for flashing this tab https://www.androidfilehost.com/?fid=95897840722648913
But first you must install Samsung USB Drivers and reboot your pc https://www.androidfilehost.com/?fid=95897840722648914
To boot your tab into Odin mode you press and hold at the same time HOME, VOL-DOWN and POWER
if through some strange miracle of techno-sourcery [see what i did there ? xD ] you manage to get the tab into odin mode,
PM ME IMMEDIATELY.
You're already basically screwed so it can't hurt to try an experiment.
In the future READ THE DAMNED THREAD !!!! ARRGGHH GROWLL [fart]
m
So what? did you ever got your tab back? im facing a similar problem while i was restoring my efs.img via terminal emulator, it gave me this error:
write error: no space left on device
So i thought there was no problem, then i wrote reboot on TE, and then nothing, i plugged the tab t331 to usb port and said installing QHSUSB_BULK driver, but it never did, so now i was searching and found only this forum with similar issue,
**i hate when they never give the solution, even when they find it, they forget to post it here
Joanse said:
So what? did you ever got your tab back? im facing a similar problem while i was restoring my efs.img via terminal emulator, it gave me this error:
write error: no space left on device
So i thought there was no problem, then i wrote reboot on TE, and then nothing, i plugged the tab t331 to usb port and said installing QHSUSB_BULK driver, but it never did, so now i was searching and found only this forum with similar issue,
**i hate when they never give the solution, even when they find it, they forget to post it here
Click to expand...
Click to collapse
you can get this driver somewhere in the motog forum. motog 2013.
sub77 said:
you can get this driver somewhere in the motog forum. motog 2013.
Click to expand...
Click to collapse
i dont need the drivers any more, i decided to make a thread because i didnt find any help anywhere...
http://forum.xda-developers.com/tab-4/help/help-galaxy-tab-4-8-0-hardbricked-boot-t3200743
Joanse said:
i dont need the drivers any more, i decided to make a thread because i didnt find any help anywhere...
http://forum.xda-developers.com/tab-4/help/help-galaxy-tab-4-8-0-hardbricked-boot-t3200743
Click to expand...
Click to collapse
but it may be possible to restore the bootloader with it.
sub77 said:
but it may be possible to restore the bootloader with it.
Click to expand...
Click to collapse
how can i do that?
one question, do you have the tab t331? if you do, coould you make the unbrick image for me?