Database Users

[DEV] Recovery + Config

I've began to work on a ClockworkMod Recovery for the A500.
The work is based on what I've written down in this thread: http://forum.xda-developers.com/showthread.php?t=1056170
As I didn't have the chance to test yet but I'm pretty sure someone wants to play with the code I'm providing it via GitHub:
https://github.com/SeraphimSerapis/Acer-A500-Recovery
This is the link to a first compiled version of it: http://dl.dropbox.com/u/1661232/cwm-alpha-2.img
>> Donate link for buying me lots of coffee <<
Everything is based on the log of the original recovery:
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p3 (null) 0
2 /data ext4 /dev/block/mmcblk0p8 (null) 0
3 /cache ext4 /dev/block/mmcblk0p4 (null) 0
4 /misc emmc /dev/block/mmcblk0p5 (null) 0
5 /flex ext4 /dev/block/mmcblk0p6 (null) 0
6 /mnt/sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /boot emmc /dev/block/mmcblk0p2 (null) 0
8 /aboot emmc /dev/block/mmcblk0p8 (null) 0
9 /recovery emmc /dev/block/mmcblk0p1 (null) 0
I couldn't check this part of the code of BoardConfig.mk because /proc/mtd is empty.
As this Device uses MMC this won't be important (IMO)
Code:
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00380000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00480000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x08c60000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
I'd be glad to hear if it worked well for you or if there occured problems.
Have fun with it,
Tim
Update: I've done lots of changes and tried to boot into my recovery.
I just got this message in the upper left corner:
secure boot: image SOS checksum fail!
This means that the bootloader is protected.
The good thing is: I could flash my recovery.img backup and I've got it working again
Update 2: I've split the recovery.img and boot.img to get some more information:
These are the files I got:
recovery kernel: http://dl.dropbox.com/u/1661232/recovery.img-kernel
recovery ramdisk: http://dl.dropbox.com/u/1661232/recovery.img-ramdisk.gz
boot kernel: http://dl.dropbox.com/u/1661232/boot.img-kernel
boot ramdisk: http://dl.dropbox.com/u/1661232/boot.img-ramdisk.gz
I updated my fstab config at GitHub based on these findings.

AWESOME!!!
Thanks for getting efforts started in getting the A500 the Clockworkmod man... This is sweet. I am not an Android developer at all (mainly in WP7) but I would love to help testing anything that is needed.
Thanks DEVS for your hard work and allowing us to costumize our devices to OUR taste!!! jejeje

was exploring my rom out of boredom.... and found the kernel config "around" someone screwed up
anyone can tell me where to find a tegra2 kernel , wana start building some modules
UPDATE: I'm gonna try working with the xoom kernel...

Locked bootloader? That's a bummer and shame on Acer! Right now I love this device so much so that it doesn't bother me but I do indeed hope the wonderful devs get it cracked. I'm happy to test if needed. Good luck and thanks guys!

I hope this gets fixed talked to bumble bee in irc today and hes tryn also. my rom is ready when we get recovery.

dc13 said:
I hope this gets fixed talked to bumble bee in irc today and hes tryn also. my rom is ready when we get recovery.
Click to expand...
Click to collapse
nice i hope he finds a solution. my recovery is ready and wants to get flashed

anything i can do to help u get it before him or help u both find something?

as i've stated here: http://forum.xda-developers.com/showthread.php?t=1059490 you're welcome to have a look if you can find the matter

Any progress on clockwork???
Sent from my A500 using XDA Premium App

The Recovery is finished already. What we need is a secure way to flash it
Sent from my LG-P990 using Tapatalk

seraphimserapis said:
The Recovery is finished already. What we need is a secure way to flash it
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
How likely is this? Could be a good enough reason to ditch the Iconia and get the Transformer which already has an unlocked boot loader.

chr0m said:
How likely is this? Could be a good enough reason to ditch the Iconia and get the Transformer which already has an unlocked boot loader.
Click to expand...
Click to collapse
I'm a developer, no fortune teller.
Sorry
Sent from my LG-P990 using Tapatalk

i'm thinking an update must be inbound... because they cant be that retarded(excuse the language) to leave the device without at least basic recovery for the user.... that will mean massive warranty work...
this is the worst part we cant experiment very deep because theres no recovery... so fingers crossed on the update...
PS: if you what my opinion any device can and will be hacked just takes the right person or the right idea... a good example is the SE X10

thor2002ro said:
i'm thinking an update must be inbound... because they cant be that retarded(excuse the language) to leave the device without at least basic recovery for the user.... that will mean massive warranty work...
Click to expand...
Click to collapse
Well if they aren't going to unlock the boot loader they had better be super fast with updates.

someone sent me an update.zip saying it was from acer.. its 300mb I have no idea really how to tell if its legit, the build.prop says a build date of 4/22, my current build.prop is 3/29. so maybe?
I'm going to drop it in my drop box, called acer.update.zip.. you guys take a look and tell me!
http://dl.dropbox.com/u/26425679/acer-a500/update.acer.zip
give it an hour to upload

So far its looking like the Android experience Google wanted to protect by holding Honeycomb source code isn't worth protecting. With an overpriced Xoom that still has nonfunctional hardware, Asus launching the TF without much of a supply chain, Samsung doing a full last minute redesign with some TouchWiz thrown in for good measure, and locked bootloader on the Iconia (which I was loving until I read this)...getting a tweaked Honeycomb seems like one of the few perks Android tabs and their users would have. I really hope the situation starts looking up fast

nycbjr said:
someone sent me an update.zip saying it was from acer.. its 300mb I have no idea really how to tell if its legit, the build.prop says a build date of 4/22, my current build.prop is 3/29. so maybe?
I'm going to drop it in my drop box, called acer.update.zip.. you guys take a look and tell me!
http://dl.dropbox.com/u/26425679/acer-a500/update.acer.zip
give it an hour to upload
Click to expand...
Click to collapse
Downloaded...But how would I go about flashing this? I'm willing to sacrafice my tablet and try this out for the greater good of man kind(or our Iconia community. Which ever you prefer. )

kxs783kms said:
Downloaded...But how would I go about flashing this? I'm willing to sacrafice my tablet and try this out for the greater good of man kind(or our Iconia community. Which ever you prefer. )
Click to expand...
Click to collapse
If I remember correctly when you boot hold power and vol down it will boot into an update mode looking for an update.zip on the SDCard. Perhaps if you renamed it update.zip and put it in the base directory of your sd card it might attempt to update.

I'll be having a look into that file..
Regards

that is what I was hoping for, I wouldn't just go flashing it, perhaps sir seraph can figure out If in fact its an update, and maybe it can bring some good

[Q] ra 3.16 recovery encryption problems

Tonight i was going to flash the newest flexreaper ics build on my iconia tab. While i was waiting for it to download, i decided to play around with the ra recovery options. I tried to upgrade the internal storage to ext4 but it said that it failed at data so i formated all of them back to ext3 but data still wouldn't mount and still won't. When i booted the rom up it said that there was a problem with the encryption and it needed to reboot. I tried an older honeycomb rom but now it asks for an password to decrypt the tablet but i never put one on. Is there anyway to get around it because it is unusable right now?

darktwolf380 said:
Tonight i was going to flash the newest flexreaper ics build on my iconia tab. While i was waiting for it to download, i decided to play around with the ra recovery options. I tried to upgrade the internal storage to ext4 but it said that it failed at data so i formated all of them back to ext3 but data still wouldn't mount and still won't. When i booted the rom up it said that there was a problem with the encryption and it needed to reboot. I tried an older honeycomb rom but now it asks for an password to decrypt the tablet but i never put one on. Is there anyway to get around it because it is unusable right now?
Click to expand...
Click to collapse
I thought Drellisdee put warnings about messing with those things. Check his RA Revamped thread, and I think he put some answers. More specifically in the very first paragraph, with a link to the fix
http://forum.xda-developers.com/showthread.php?t=1459821
Here I believe is the part you need, quoted from the post;
"Those are advanced options that most users shouldn't have a need for and shouldn't normally use. Your data should have already been ext4 and you tried to reupgrade it to ext4 and looks like you corrupted your /data partition. For reference the 1st page has a description of the menu items. Dont just go selecting every option if you dont know what it does.
To fix your blunder you will need to boot into my recovery and open adb shell.
This will cause loss of all data contained on /data which will lose your /data/media.
From adb shell
Code:
mount (this is to check data isn't mounted) if mounted use "umount data"
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8
After this is done your file system on /data will be fixed."
Click to expand...
Click to collapse

Moscow Desire said:
I thought Drellisdee put warnings about messing with those things. Check his RA Revamped thread, and I think he put some answers. More specifically in the very first paragraph, with a link to the fix
http://forum.xda-developers.com/showthread.php?t=1459821
Here I believe is the part you need, quoted from the post;
Click to expand...
Click to collapse
i tried that method but it didn't find my device in adb but i found another way. If you hold the power and volume up button on boot and switch the rotate lock over it erases all file systems. I tried that and it booted up like brand new.

darktwolf380 said:
i tried that method but it didn't find my device in adb but i found another way. If you hold the power and volume up button on boot and switch the rotate lock over it erases all file systems. I tried that and it booted up like brand new.
Click to expand...
Click to collapse
Yep, that sometimes fixes it also. Sometime
ADB sometimes takes 2 or 3 plug ins to connect. Was messing with it earlier today, and had the same issue, but eventually it found the tab.
Glad you got it going.

Crashing Nook

Well, my Nook appears to be in trouble.
The long and the short of it is that it got wet. Not too wet, but wet.
It boots but whatever I boot to crashes. This includes sdcard installs. The ROM completes the boot, and I can sometimes even open the app drawer, but it crashes before I can interact with it in any meaningful way.
All ROMs complain of "System process" and Wireless issues, with FCs.
I cannot get adb to recognize the device anymore. lsusb does find the Google Inc. entry, though. When I try and run adb devices (ubuntu), it returns ?????? and says insufficient permissions. I have, in response, set up the 99-android.rules in etc/udev/rules.d but it still cannot connect. I have also tried to quickly access the android terminal in the brief period I am allowed before the device crashes with no luck. My goal with this was to try fdisk -l.
The sdcard never mounts while in the ROM, and the emmc storage appears completely wiped.
However, I was able to see I had the correct files in /rom once, so those are there.
Thinking that the wireless chip might be the problem (as when even when I return to stock the set-up fails there, well, until it crashes again...) I tried to just turn off Wifi in 7.2. But as I unchecked the box, right under the setting just displayed "error"
CWM appears to be working EXACTLY as it should, including mounting the sdcard and allowing me to choose update zips.
The uboot and the uboot menu work as well.
I have tried flashing CM7, 9 and stock, as well as booting from sdcard in CM9. All flash and boot normally, but crash.
I have done the 8x reboots, succesully, but when the B&N set-up begins, I cannot connect to wireless. Which would be okay, in the long run, but it then crashes, which is not okay.
I was hesitant to reveal that it got wet, because I can see this being written off as a hardware issue (which it may be, don't get me wrong). But the fact that CWM works and the ROMs boot sure look like software problems to me.
I have tried flashing just about everything that looked promising. I have not dd any images, because I cannot get adb to work, and don't have any idea which partitions are in what shape.
Any suggestions?

Position the unit upside down with the SD flap open. Blowdry it from the bottom up on medium several times over a couple of days. If it's still doing it after that you can probably eliminate moisture as a cause.

old cell phone trick
Fill a bowl with rice (uncooked).....the rice will draw the moisture out.

you can also submerge it in ispropol rubbing alcohol... is what we use to clean electronic components... it will combine with the water... also used for water in gas on a car

Whoa, isopropyl alcohol. I feel like that would take some stones...
I have already put it through a 30 or so hour rice regimen (if that is true, even. It makes some kind of weird intuitive sense, which is usually the kiss of death...)
I have it standing up now and will see about a little air dry method while I investigate where to find the alcohol.
It didn't get submerged, it was lying on a counter and a glass got knocked over. I grabbed it right up, and then left it off like I said.
It boots, CWM works, but since it has been set all the way back to stock and all iterations have the same issue I am fearing the worst...
Thanks for the ideas...any and all welcome!

You can take the back off. I have not done it, but somebody just said they did it to disconnect the battery to reset. Look at that recent thread in q/a. Maybe he can tell you how he did it.

Attempt at your own risk, no support will be provided.
I'm not the battery guy leapinlar was talking about but,
Open the battery flap, remove SD card, remove the tape dots from the T-5 torque screws then remove the screws. Slowly and carefully so as not to break any of the hooky thingies that are holding the back on pry the cover up from that point moving slowly around the unit.
I've only done this once, it was a while back and I ended up breaking two of the little hooky thingies. That's why I suggested providing points for evaporation to escape and attempting to accelerate evaporation. Heck we don't even know if moisture is the issue anymore.

Thanks for the extra suggestions.
I tend to think at this point that whatever water got in there is gone. It's been four days, and it wasn't soaking. I may just go ahead and try and take out the battery, I don't know exactly why that would help, but what have I got to lose?
If I had to guess, I would think that the wifi chip might be shorted, as that is the only thing that doesn't seem to work at least for some period of time.
The FC's sure do look software related though. I fail to see how CWM could read and mount the sdcard while the ROM cannot as being anything other than sotware. Unless they use wildly different methods to do the same thing.
This nagging feeling that I should be able to at least fix that with some software methods keeps me thinking the same or the other problems. I'd be okay with an non-networked tablet, if it came to that. But maybe the thing has to have wifi as an option to work right. I don't know...

Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.

Malave said:
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Click to expand...
Click to collapse
Considering that this is basically what is happening to me (but with some additional Wifi setting crashes) this gives me hope.
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
Anyway, of interest (before I shut it down 2 days ago):
internal sd card is not wiped, it can be explored in CWM.
The /ROM partition is at least somewhat functional, as battery stats can be wiped
When I request a log, I get:
Code:
Battery Stats
Block Groups: 3
reserved block group size: 23
Created filesystem with 11/22608 inodes
and 2883/90357 blocks
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure. Maybe that is why I am having trouble with ADB. It just kept saying insufficient permissions and ???????????. I tried setting up android-rules for udev with no luck.
Unless I hear anything else promising, I will go get the proper screwdriver and try the battery thing. It has been sitting off for a couple days now...
Thanks for all the ideas, people.

I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Try your edits to /rom... and if you have to try: mount /dev/block/mmcblk0p2 /rom

DizzyDen said:
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Click to expand...
Click to collapse
I actually didn't try to do anything. I just wiped system, cache, davlik, battery stats and asked for a log prior to flashing a new zip in the hopes that the rom would work if provided a blank slate.
I wiped battery stats since the .bin that holds them is in /rom. The log was something I had never done before.
The notes from above were just the CWM output from the log.
edit: I just saw your second paragraph. Don't know how I missed it.
But I don't know what you mean by edits. I haven't been able to get ADB working. I have been able to mount and unmount through CWM that's it. Unless you might know anther way to resolve insufficient permissions with beaucoup question marks instead of device number?

Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.

DizzyDen said:
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
Click to expand...
Click to collapse
Which I was. I got it from Leapinlar, and was under the impression, since I had seen him warn that roms flashed from that recovery would go to emmc, that it would work.
I did make a regular 3.2.0.1 bootable, and tried again, but with the same result, so I don't know if that made a difference. But it did seem hopeful, so thanks for the response.
I am going to finally go get the torque screwdriver and take this battery off and give it some days. It's been almost a week already, but you never know.
Thanks a bunch for the reponses, Diz.

mateorod said:
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)[/CODE]
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure.
Click to expand...
Click to collapse
Mateorod, if you got that log using my CWM boot SD version 5.5.0.4, the recovery.fstab lists /dev/block/mmcblk1p2 as SD-EXT, which for some devices is the extended partition on SD for storing additional apps to supplement /data. Our implementation of CM does not use that. So when recovery tries to do some wiping, formating, backing up, etc, it always fails when it looks for that partition. It has nothing to do with /system or /rom.
If you told it to do a factory reset, it tries to wipe /SD-EXT as part of that and it fails to wipe that because it cannot find that partition.
Edit: That CWM SD does do its modifications to emmc. It only referenced mmcblk1p2 because of sd-ext.
Here is the filesystem table from my log using it on SD:
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0

The alcohol trick does work, I did it on my old HTC Kaiser. I disassemble it as much as I was comfortable, and then completely submerged it in alcohol until It stopped throwing up air bubbles; Thus showing there was no air left in the unit. I then removed the pieces from the alcohol and put them in a bowl of rice. I let it stand for about a week. Once the time was up a reassembled and turned it on like nothing had happened.
Little note: I was in the possession of a AT&T Go Phone for use as a back up in case this destroyed the unit. If you feel that there might be another way to repair it, I would suggest you explore that option first as I do not know what a significant time in alcohol will do to the inner workings of the Nook. However if you are at the point of already replacing or upgrading to a different tablet, than you have nothing to lose and can only gain a working Tablet or fancy Paper-weight from this.

Okay, a little update.
I had taken apart the Nook and let it sit for almost a week. But upon reconnecting the battery and clearing system/cache/davlik and reflashing anything, it still wouldn't allow in-ROM mounting of sdcard or adb or wireless and I would still get some version of "process System not responding" and "Setting Wireless not responding" toasts and then a crash, either in CM7, CM9 or Stock. Unusable.
What I think I have is a totally borked wifi chip. Which is okay, in the long run, but the Nook kept crashing and I would have liked to use it in some capacity.
What I decided (which was difficult to diagnose with no terminal or no ADB) was that the Nook was crashing upon trying to access the network and the saved network info. (which I know is mad persistent, as the wifi network I used to originally register the device still shows up in the stats, even after many many system wipes and 8x reboots and so forth.)
I had never reset to factory from stock settings and I couldn't now completely erase and deregister because you need wifi to do so.
However, I found this (which I had never heard of, sounds like a boon to thieves everywhere). After skipping out-of-box experience I could boot into stock recovery and finally erase the wireless settings.
Now I have a stable (albeit un-registered) stock nook, where I can at least read the books I have on sdcard.
I will eventually reflash a CM build now that the network settings have been forgotten and see if that is usable, even if there is no wifi.
But I am pretty happy to have some semblance of the Nook back, even if it is just a neutered (literally) stock.
I'll let you know how CM goes one day soon.
Thanks for the help!

Excellent, (and powerful), link.
And by virtue of that link I will find a way to proclaim my absolute geekitude within the company by dropping Kate's name. :good:

Well, I finally tried flashing Cyanogen 7 and 9 to the thing, but as it crashes when it tries to access wifi, I can't get it stable.
Unless anyone knows a code edit (smali maybe? I know there are a bunch of boolean settings in the SystemUI.apk, maybe there) where I can change the default wifi setting, I may just be stuck with stock.
Which is way better than nothing, at least it has use. Skipping OOBE was a life-saver for getting to a place where I could erase the WiFi info.

Okay, here's another shot in the dark, still trying to get this thing to successfully boot in CM...
I am working on a little project for the Nook, which will be infinitely easier to debug if I can actually boot into CM.
Does anyone familiar with the source code know how to modify it so that WiFi is set to off by default? I am thinking about changing the 'true' to 'false' in the /device/bn/encore/overlay/frameworks/base/core/res/res/values/config.xml entry for wifi found here...
Code:
<!-- This string array should be overridden by the device to present a list of network
attributes. This is used by the connectivity manager to decide which networks can coexist
based on the hardware -->
<!-- An Array of "[Connection name],[ConnectivityManager connection type],
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
before automatically restore the default connection. Set -1 if the connection
does not require auto-restore. -->
<!-- the 6th element indicates boot-time dependency-met value. -->
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,1,-1,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<!-- item>"ethernet,9,9,2,-1,true"</item -->
</string-array>
This looks like I am on the right track (this will eventually end up being compiled into the res folder of framework-res.apk) but I may need to track down the ConnectivityManager. Although the cursory look I have given this seems like I may be close to on the right track...
(The wifi being on at boot always crashes my CM installs due to shorted wifi chip, for those of you who may be new to the thread.)
I am asking here just in case someone knows, I may just go ahead and try it if no one chimes in. But better to ask than to blindly shoot in the dark, I figure...
Update: Success. I am back on CM9 (well, a hybrid, actually...HINT), without wifi.
Update 2: Due to the fact that this nook is now in a Cyanogen-usable state, a new rom will be posted in development tomorrow from eyeballer and I. Thanks for the suggestions, everyone. I wish I had dipped it in isopropyl alcohol, just so I could say I did it...

Samusung Galaxy Tab 4 8.0 - SMT330NU Bricked (Black screen of death)

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?

[SOLVED] No GSM/3G Signal

hi
I tryied to flash a rom and the phone stoped during the process... i thought it was the end...
The phone was died... no response, not recognized by the PC...
A day later i tried again and the PC recognized it, so i flash "Gionee_E7_32G_0301_T8143.zip" with Kitkat Full wipe, and it came alive...
Everything seemed to be working fine except the GSM and 3G signal... The IMEI was gone so i used "EFS Professional" to restore it...
Now the IMEI is OK but still without GSM/3G signal...
I believe that the EFS partition was screwed up...
Can anyone provide me a NANDBACKUP of the EFS done with the TWRP recovery?
I guess that will fix it...
Anyone suggestions that would fix this are also welcome.
Thanks
==============================================================
Solved thanks to user jdgomez001
Read this thread, the qcn file is posted twice

Come on people... Help me out please
Please a backup of the EFS partition will containe your IMEI, but be assured that i will changed to mine own....
You can even change change your IMEI to zeros, make the backup and then restore your IMEI...
Can anyone identify the Modem/Radio chip on this phone? Maybe i can get an update...
Or if anyone can give me some information about how to restart or reconfigure the GSM Radio, maybe a modem flash or something...
Please people....

You don't know how to read or use search function.
I have already posted the solution somwere else.
You just need to config your APN (acces point names) for your network provider .
Do this from settings.
You should find the settings on your operator website or somwhere, or just ask for them on someone with same phone or network provider. IT is very easy.

Muresan01 said:
You don't know how to read or use search function.
I have already posted the solution somwere else.
You just need to config your APN (acces point names) for your network provider .
Do this from settings.
You should find the settings on your operator website or somwhere, or just ask for them on someone with same phone or network provider. IT is very easy.
Click to expand...
Click to collapse
For a few moments i thought that i went nuts...
Its quite unfair to say that i dont know how to read or use the search system... but whatever...
Those settings are on the SIM. The SIM is OK! I've tested the SIM on other phones and its ok.
Just to be sure I've checked the APN settings and their also correct..
Thanks anyway for your input.
Now i'm going to flash the GSM RADIO... Not sure what will happend but by now i'm quit desperate...

People i refer to this link
http://forum.xda-developers.com/showthread.php?t=2374063
Can someone please make a NV backup with QPST and share with me, please?

I have the same problem any1 can give a virgin or stock nv backup?? mi imei was lost, and when i recover them i cant get GSM SIgnal... maybe i think.. some nv_items related to Network are bad i need only a backup please help me too

I will help You but You must help me do the back-up . i don't know how to do this.

Muresan01 said:
I will help You but You must help me do the back-up . i don't know how to do this.
Click to expand...
Click to collapse
Hi thank you so much... Please add me on facebook and i will help you... to you help me please make a backup dont is hard... i have a new hope... with you
facebook.com/AdminSkynet

Muresan01 said:
I will help You but You must help me do the back-up . i don't know how to do this.
Click to expand...
Click to collapse
Thank you very much for this.
I really apreciate that
Check out this topic
http://forum.xda-developers.com/elife-e7/help/request-efs-backup-imei-zero-img-twrp-t3088125
See if you can do one of those backups.
If you have TWRP Recovery is very easy:
1 - Reboot into Recovery Mode
2 - Press Backup
3 - Select only the EFS partition
4 - Rename the backup (optional) and press Backup
Thanks

https://docs.google.com/file/d/0BxwIZ519ngvyMnowZ0lnS252WVk/edit?usp=docslist_api
This is the link to efs back-up.
IT is compressed with 7zip.
I Hope IT will work.
Oh i almost forgot!!!!!
This is the 4.4.2 back-up !!!!
If is needed i could try to make 4.2 android back-up.

Muresan01 said:
https://docs.google.com/file/d/0BxwIZ519ngvyMnowZ0lnS252WVk/edit?usp=docslist_api
This is the link to efs back-up.
IT is compressed with 7zip.
I Hope IT will work.
Oh i almost forgot!!!!!
This is the 4.4.2 back-up !!!!
If is needed i could try to make 4.2 android back-up.
Click to expand...
Click to collapse
WOw man thank you so much... i will try the files... thanks, thanks thanks, :good::laugh:
---------- Post added at 11:02 AM ---------- Previous post was at 10:47 AM ----------
dont work for me :crying: man this backup from working gione e7? all values is in 0 why???
can you share a 4.2 backup from working gionee e7 please (( :crying:

Yes i will flash 4.2 rom and upload the back-up.
Yes,this is from working phone.

Muresan01 said:
Yes i will flash 4.2 rom and upload the back-up.
Yes,this is from working phone.
Click to expand...
Click to collapse
thank you so much my friend.. i put ur backup from 4.4 to my phone 4.2 and doesnt work... maybe i need a backup from 4.2 sorry for problems

Muresan01
Thank you very much for your share. I've been working around the clock with your backup to make my phone work again but still no luck...
Now i'm about to give up, throw this piece of sh*t to a wall and get on with my life....
I've been 'inloved' be this phone for about half a year... In the first week this happens...
My last attempts:
Flash Full Dump ROM
Write default NV values
For this i need your help [again] to provide the needed files.
Flash Full Dump ROM
- To do this you will need Busybox installed [its free at PlayStore]
- ADB access from a PC
Then just use this command line for each partiton:
/system/xbin/busybox dd if=/dev/block/partition of=/storage/sdcard0/partition.img;
Click to expand...
Click to collapse
Partitions to backup
DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p5
boot -> /dev/block/mmcblk0p7
cache -> /dev/block/mmcblk0p15
dbi -> /dev/block/mmcblk0p3
fsc -> /dev/block/mmcblk0p18
fsg -> /dev/block/mmcblk0p17
grow -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p10
modemst2 -> /dev/block/mmcblk0p11
pad -> /dev/block/mmcblk0p9
persist -> /dev/block/mmcblk0p14
recovery -> /dev/block/mmcblk0p16
rpm -> /dev/block/mmcblk0p6
sbl1 -> /dev/block/mmcblk0p2
splash -> /dev/block/mmcblk0p21
ssd -> /dev/block/mmcblk0p19
system -> /dev/block/mmcblk0p12
tz -> /dev/block/mmcblk0p8
udisk -> /dev/block/mmcblk0p20
userdata -> /dev/block/mmcblk0p13
Click to expand...
Click to collapse
For more information on this subject click HERE
Write default NV values
For this it will required DFS CDMA Tool Download HERE
Knowledge level: Intermediate/Lightly High
{
"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"
}
1 - Connect the phone on Diagnostics port
2 - Send SPC and Password
3 - Go the NV separator and press "Read RF"
4 - Then press "Save" and choose a location to the file
The file should have 200/300/400 KB
The default saving location for this file is:
C:\Program Files (x86)\Telecom Logic\DFS\NVF
C:\Program Files\Telecom Logic\DFS\NVF
Rooted phone required for both options.
Please, some of you already know how this problem been disturbing me... a lot...
I'll appreciate the help for this... [Don't really wanna throw my phone to a wall]
Once again thank you all

Please guys...
Some help here....

Solved thanks to user jdgomez001
Read this thread, the qcn file is posted twice

Thank you everyone!
First off, let me take my hat off to the owners & keepers of this wondrous haven.
I belong to the generation that experienced the transition from analogue to digital, and was always reluctant to give in to the constant monitoring of today's smartphones. That said, about two years ago I inherited a Blu life Pure Xl 16gb, a month or so a go I made the mistake of signing off my Mercado Pago account, and somehow signing in since then became impossible, I couldn't get past the the sms/call confirmation stage. So, being that I resurrected a Blu Studio 5 for my mother about half a decade ago with the excellent help of this community, I decided to give it another go, this time with my very Blu/Gionee cellphone. To cut the story short I was testing roms to see which performance was best when I hit a scarry patch... one of the AOSP Roms for Gionee7 literraly broke my phone, corrupted the EFS and it took me 4 nights of research to reach this very thread, and gzus, how helpful it has been.
So thank you again to everyone involved, this thread should definitely be a sticky within the Gionee7 section and please, please for the sake of whoever experience the same thing next keep those links to qnc, backups and tools alive cause believe me, they're lifesavers.
Cheers, long live XDA, 4PDA and everyone focused on wide open sharing of knowledge.
You're what's keeping mankind afloat these shady days.
Stay safe.