I think my G Tablet may have gotten perma bricked.
So far I have done:
Clockworkmod to SD>TnT Full Vanilla Restore>TnT Lite Flash
Then
NvFlash in APX Mode>Flashed to stock and removed clockworkmod
I also tried to reflash to TnT Vanilla and Lite after the Nvflash.
Yes I used a mirco SD and partitioned it, wiped all data before a flash. I'm thinking about returning it since I just have 2 days with it and still got the 30 day warrantee from Sears. It all started with a Google Services Framework crashing while trying to connect to an adhoc network.
Related
Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
About 2 months ago, I got a Samsung Infuse 4g. I was thrilled. At first I was satisfied with the stock rom and its limited functions, but then I got really interested into custom roms. I rooted my phone, installed Clockworkmod recovery and flashed Cyanogen 7 rom. During the reboot process, I pulled out the battery just like the tutorial said and thats where everything went wrong. My infuse got stuck into the bootloop, but I was able to get into recovery. I flashed Cyanogen 7 again and it work. However, my home, back, search and menu buttons all stopped working. I figured it was the customed Rom, so I flashed MiUi. The buttons still did not work. What is worst of all, is that My computer refuses to recognize my phone(yes I installed Samsung Kies)(download mode is unrecognizable too). It only recognize it as a storage device. As a result, Odin does not pick it up. neither does heimdall. I need some serious help. I have tried everything. I am currently running Miui and apparently, now I can't get into recovery mode. Guys, please help.
if you cant access the phone from usb and you cant get into recovery then you re screwed.I had a similar problem and had to return the phone to vodafone to fix it
After screwing around with it, I factory resetted and Tried download mode on a different computer and luckily it worked. Odin was able to pick up my infuse and I used Ultimate Debrick. Thanx a million to those within the Community who are consistently developing and coming up with programs such as Odin. Big thanx to everyelse who shares their thoughts and advice.
I had my 4G xoom unlocked and rooted, installed Tiamat 2.2 on it (which then killed the 3G) so I decided to flash back to stock, but somehow screwed up the backup, managed to go back to factory 3G image with the HRI66.zip file I found in another thread. It unrooted my phone and relocked it, but now it's in a constant reboot loop, showing the honeycomb images for nearly 45 minutes now. What's my options? My computer wont talk to it, because I can't even get into it to enable USB debugging.... UGH!
sooo..... I let my device run dead.... then powered it up, went into fastboot mode, which took me straight to the unlock screen.... because I didn't lock it when I unrooted it.... All fixed..... except still NO 3G!!!!!
I had AOKP Build 29 installed on my Transformer and I decided I wanted to go back to stock so I attempted to flash the stock FW through CWM. I ended up with a CWM bootloop and like an idiot I didn't make a back up of my previous setup. So I tried flashing back to AOKP with the rom I had saved on the tablet and still got the same thing. I cleared data and tried flashing an old version on Android HD that I had on the internal SD card and that still didn't work. So I then figured I'd try flashing stock FW again....This is where things got weird. It seems that it only flashed the recovery. So now I'm stuck with stock recovery, but as soon as it boots into recovery I get the android w/! and ADB won't recognize it. I also tried doing an NVflash, but after I put the tab in APX mode and start the NVflash the tab disappears from my list of devices on my PC running windows 7 64bit. Any help to fix this will be awesome. The only thing I can think of is to uninstall the drivers and reinstall them to see if that fixes it.
I got a similar problem today. I put it to APX mode, start nvflash, it flashes the first images and when it starts flashing the bootloader my TF disconnects and turns off.
Please help!
Bump. Over 230 views and no ideas yet?
Sent from my Galaxy Nexus using Tapatalk 2
Hi guys,
Really sorry to ask about this but tearing my hair out!
I have a P6200 UK model. I installed CWM v6.0.1.0 and it worked fine. The intention was to install Galaxy ROM HD (build #06), so I downloaded it, put it on my SD card, and installed from CWM recovery. The install got stuck on "Flashing boot" - so after around 15 mins I reset it.
It went into a boot loop on the initial Samsung logo. Luckily I'd previously re-flashed stock HC with Odin (to cure a dead Wifi problem caused by, I think, an errant install of Busybox) so I did this again, rebooted, and the system came up, text started scrolling up the screen, followed by a red error message (see picture) and a reboot. I was then once again stuck on the initial Samsung Tab 7.0 Plus log. I repeated the process and it didn't even get past the Samsung logo.
So I thought I'd try the newly released ICS Rom (GT-P6200_ATO_P6200XXLQ1_P6200OXALQ1) - this seemed to install OK, then half booted, did some text type installation stuff with the blue Android, then rebooted again, finally getting stuck on the Samsung logo with blue pulsating behind it. It never gets any further than that.
I tried flashing HC back - same result as earlier. I can also reflash CWM and sometimes it works, sometimes it doesn't. It seems I've run out of options.
So - question is - where (if anywhere!) can I go from here?
Help greatly appreciated, many thanks!
have you tried a system wipe in cwm? if not do a system wipe and reflash HC using odin.. same thing happen to me 2 days ago.. I think something is up with HD rom