Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
Hello everybody,
I am new to the forum and also new to Androids. After years of using iPhones and finally becoming fed up Apple, I've decided to try something new (please don't judge my prior smartphone selection and start posting opinions about the 2 operating systems, I do not want this thread to turn into one of the "battle of the phones" thread that I've experienced many times on iPhone forums). My friend recently got an S3 and had no use for his Galaxy S 4g, so he gave it to me so that I could try out an Android. There was one issue though, he said that the phone would not get past the Galaxy S screen and would keep re-booting itself (stuck in a boot loop). He said if I could figure out a way to fix it then it's mine.
That being said, here's my dilemma. I've tried many different methods to get the phone out of a boot loop. The first method I tried was putting the phone into restore mode and selecting the "reinstall packages" option. After this executes I get the message:
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After some further research I discovered a nice little program called Odin I read a lot about Odin and how to properly use it. After trying at least 5 different methods to get the phone into download mode with no success, I purchased a jig. The jig did the trick and instantly put me into download mode, I was ecstatic and hopeful that I could now fix the phone with Odin. I connected the phone to my PC in download mode, but Odin still didn't recognize the phone (I tried many versions of Odin, 1.85, 1.87, and the most recent 3.07). I do have the latest drivers for this phone, which I downloaded from Samsung's website. The phone will charge through the computer but the computer does not recognize it otherwise and will not allow me access its mass storage (I am running Windows 7 64 bit). I have tried using a different USB cable, and I have tried to use a different PC, the other PC I used popped up with a message saying that Windows could not successfully download the drivers (that was after I downloaded the drivers from Samsung's webpage and plugged the phone into the computer). I've even tried transferring stock firmware onto an external SD card and loading it onto the phone from restore mode (is that even possible to do?). I have also tried running Odin in compatibility mode, still didn't detect the phone. I should probably also mention that Kies Mini also does not recognize the phone. I asked my friend if he ever tried rooting this phone and he said no, so I'm assuming this issue has nothing to do with a failed attempt to root.
I really want to get this phone working, but I have run out of options to try. I am hoping that someone on here has a solution for me from a similar experience. After reading through the forum, I have noticed that people on here are very helpful and also very friendly; something that I can say is very different from some of iPhone forums I've used. I apologize if there is already a similar thread to mine, I've read through many threads and none of the solutions have worked for me. I also apologize for my first post being so lengthy, I just wanted to state all of the methods that I've tried to fix this phone. Thanks for your replies.
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
itzik2sh said:
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
Click to expand...
Click to collapse
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
It sounds like you can't use Odin because of a windows issue. Try installing linux. I use ubuntu
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
You can also run as live CD or in a virtual machine
Sent from my HTC One X+ using xda app-developers app
hubbs134 said:
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
Click to expand...
Click to collapse
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
I second this... This should fix your driver issues.
Thanks for both of your replies. Odin detected my friends GS3 so I know it's not a Windows issue.
itzik2sh I did what you suggested and now got the command to function properly. I am going to try and finish the tutorial, I will be back soon with results. Thanks.
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Irish Enigma said:
I second this... This should fix your driver issues.
Click to expand...
Click to collapse
I forgot to mention that I can here the sound that a device was just connected to the computer via USB, and a message pops up saying USB device not recognized. When I click on the message it says "One of the USB devices connected to this computer has malfunctioned, and Windows does not recognize it."
Tried a different port? Tried second different port with a different USB cable?
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
Theraze said:
Tried a different port? Tried second different port with a different USB cable?
Click to expand...
Click to collapse
Ok I got the device connected and I got Zadig running, however, there is no option for "Samsung USB Composite Driver" on the drop down list, on "gadget Serial", "Gadget Serial Control (interface 0), and "1.3 HD Webcam (Interface 0)'. What should I do?
On the one-clicks, you don't actually want to use zadig. Apparently it conflicts, which is awesome for something that gets released WITH the tool.
If you're doing manual Heimdall, make sure you've told zadig to list all devices in the menus. Your phone should show up after that.
If you're using a one-click, make sure you're using a USB port on your computer where you have NOT installed zadig, Kies, or Samsung official drivers. Follow the steps in the one-click religiously, and it should cooperate.
Follow the guide %100 then Odin should work
Sent from my HTC One X+ using xda app-developers app
Ok I ended up getting the phone to register in Odin. I flashed it with the stock rom in Odin and it said success. The phone booted and it seemed like it was going to work but then the recovery menu came up. I posted a screen shot of what it says, what action should I take from here? Thanks
I am also in a different boot loop now, before it would load to the first screen (black screen saying samsung galaxy 4g) then restart, now it boots to past the splash screen to where it says "Samsung" and then reboots back to the screen where the pink letters roll across the whole screen. I don't need to flash bootloaders do I?
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
EDIT: Samsung's are easy to brick and hard to debrick it may take a couple of trys
Sent from my HTC One X+ using xda app-developers app
Irish Enigma said:
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
OK GREAT NEWS! After flashing with Odin and that screen popping up, I clicked update from SD card, which failed. I then click system reboot, which brought me into the new boot loop. I put back into download mode and re-flashed with One-Click. Same recovery menu came up as before but when I clicked reboot system it hung at the "Samsung" black screen (after the splash screen) for about 20-30 seconds and then booted up I'm afraid to turn the phone off and see if it reloads lol. Is it safe to say that it is fixed? Or should I still follow your advice and run the proper recovery in Odin and then sideload a new rom? Or take different action? Thanks for all your help guys! Everyone gets a thanks click for being so helpful and friendly on an unhappy/confused/pissed off/ now happy new Android user!
Ok I just put my Tmobile simcard in and the phone is not detecting the sim. Any suggestion?
The IMEI number and baseband both say "unknown", I'm assuming this has to do with the simcard not registering?
hubbs134 said:
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Click to expand...
Click to collapse
What Heimdall package are you applying ?
After JAR package runs you are ready to go.
As I wrote, according to guide you can reinstall "Gadget" driver.
EDIT :
Enigma, if you're not an owner of an SGS 4G please stop advising.
Odin is not the common way since we have MTD ROMs and it had its problems.
hubbs134,
blank IMEI is a serious problem. without a proper IMEI your device is everything but a phone.
Try this : take battery off, press the POWER button for 10 seconds, leave device untouched for 15 minutes and then put battery back and power up.
This could bring your IMEI back to life. If not... maybe another flash will help.
P.S
The 3e recovery image you put on post #14 is a snapshot of the the stock unrooted ROM recovery.
Hi there,
Today i've received this tablet. All good and dandy until it notified me it has an update so obviously i've gone and do the update. Surprise.. after reboot, update installment and so on the device won't boot anymore at all, and recover mode doesn't work to enter.
I've found official ROM package on their site:
ftp.vonino.org/public/Firmware/Vonino_Tablets/Pluri%20Q8/Orange%20Version/Android%206.0/
Tablet can connect to the PC, but it isn't recognized because "some drivers" missing. How can i install this ROM on the tablet from my pc ?
Thank you.
Hi,
I can't find anything about it on xda or anywhere. You'll need to contact the manufacturer for drivers and instructions on flashing their firmware.
Good luck!
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
denede said:
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
Click to expand...
Click to collapse
Typically, on devices I know of, it's fastboot that you would use to flash factory images. So you should be good there. But again, I don't know if that is how your device works too. And it would also typically not matter what's been altered on your device, system wise, you would simply flash the appropriate images with fastboot.
So I'd still say you need to determine the correct procedure to flash the files you got from their site. Perhaps there site has instructions? Or a support number for help of its not working as it should?
I've talked with the support. They gave me a link with an official ROM, a different one that the one that was from the site. But they didn't even told how to use it, LOL.
Have the damn files and don't know what to do with them, OMG.
I've placed the zip archive on SD card and tried to use the option from rescue mode with 'update via sd card". The zip archive is visible but after i select it says Installation aborted :|
I've googled around and maybe my tablet needs to be at over 50% power... but it was plugged into the wall it should've worked.
edit: 100% and no good...
edit2: they sent me another e-mail with a pdf file in which it is explained how to flash their device.
Hi
TF300T JB 4.2.1
Bought new in the US in 2013 so has US SKU. Originally for my wife, but she now has an iPad Pro so I've got the hand-me-down!
Wiped it and unlocked the device successfully using the Asus V8 utility. Tried to flash TWRP from Win7 computer but something went wrong. The interface was still there, it would boot up okay but there was no sign of TWRP. Eventually, I went into fastboot and selected RCK. Nothing happened except the icon turned brown and just sat there. Then I tried a factory reset but it wouldn't have any, nor a cold boot. In desperation I turned the device off and tried to reboot. The initial "Asus" screen came up ("This device is unlocked" in top left-hand corner and the 'Nividia Tegra' logo in bottom right. No spinning circle of dots). It won't boot into fastboot, in fact the volume keys are totally unresponsive. On/off will turn off the device, but it immediately boots back to the same Asus screen. It's not recognised by the Win7 computer so I can't flash anything to it. I think I've tried everything this forum (and a few lesser ones!) could suggest, to no avail.
I believe I now have the proverbial 'bricked' tablet.
Nothing daunted, and not prepared to involve Asus support, I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
I'm no expert on the Android OS so any help from you experts would be much appreciated.
Thanks in advance.
Anyone?
I know the TF300 is a bit long in the tooth now, but all I want to know is whether a bricked one can be recovered by replacing the motherboard. There must be someone out there who has done the replacement and can advise me? Also, I apologise if this in in the wrong section, I guess it should have been in the 'Help' section, but I didn't realise until I'd posted it.
capelyddol said:
Hi
TF300T JB 4.2.1
I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
Click to expand...
Click to collapse
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
ebonit said:
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
Click to expand...
Click to collapse
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access. The initial boot-up screen is all I get, in perpetual loop. The only way to shut it down is reset with vol-up., though it's possible it may be in some sort of variation of apx mode at this point as the screen is blank. I've no way of knowing as my win 7 computer only acknowledges an 'unknown device' at that point, and nothing when the initial boot screen is there. Vol-down doesn't seem to have any effect at all. Windows has already installed the drivers so won't re-install, or uninstall them as it's 'unknown'. I did once manage to get it recognised as an 'apx device' but with an '!' (not sure how I did it as I haven't been able to replicate it since!) but I don't think that helps me even if I could replicate it without the '!', Nvflash requires I have the necessary back-up files, which of course I don't. I don't know where to go from here except to replace the motherboard. Once I get the device apart I may try disconnecting the battery, vol-down, and reconnect, to try booting to recovery, but I'm not optimistic of that working.
I'll certainly be very happy to consider any other suggestions you, or anyone else, may have.
I tried Buster99's method, but as my TF300T isn't recognised by Windows that was a non-starter.
Once again, many thanks for your input.
capelyddol
(John)
capelyddol said:
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access.
Click to expand...
Click to collapse
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
ebonit said:
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
Click to expand...
Click to collapse
ebonit ~ Thanks for the links. I checked out huebinger's and pulled my motherboard out, then bought the one you linked to on eBay. Hopefully, I didn't do any damage getting the MB out. I'm more used to the tough old internal wiring of desktop computers!
I'd already backed up the data and done a factory reset before I began my abortive attempts at rooting so hopefully I'll be starting with a clean slate once I get the new board installed. It's going to take a while to cross the pond to France, but I'll report on how it goes once it arrives.
Thanks again for your help, it's much appreciated.
John.
(capelyddol)
Hello,
My tf300t got bricked while upgrading twrp.
nothing helped, i put away the tablet, after a year i found her ... so i said to myself "why not" ?! so i ordered from ebay a motherboard, and it's work like a charm, but the tablet is old now ;0
now i want to setup a lite rom ....
mitomon said:
Hello, now i want to setup a lite rom ....
Click to expand...
Click to collapse
What do you mean?
What do you mean?
Click to expand...
Click to collapse
I was wondering that, too!
It's good to know the s/h motherboard cured his tablet's ills, though.
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
Go to folder /Universal Naked Drivers 0.72 you unziped at start on your Desktop.
Select file android_apxusb.inf, then right click -> Install.
Force driver install and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Click to expand...
Click to collapse
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
Click to expand...
Click to collapse
Congratulations! You did a good job. Thanks for your report.
First of all, to avoid any issues to get your device on N 7.1 Nougatella please follow exactly Tim's install instruction step by step in post #1. https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
You need Kang TWRP as advised by Tim. Don't forget to format data through Kang TWRP before. It takes up to one hour. Then change file system to F2FS for data only no cache and system. Successfully done your device is now ready to install Rom, pico Gapps and SuperSU fresh downloaded via Tim's links there.
PS: About your USB issue take another USB port on your PC not via hub!
Good luck!
Three days with nothing from me, you'd be excused for thinking either I was dead, or my tab was! Thankfully, neither. In fact - SUCCESS!!! We're both alive and well, and for the tablet at least, performing better than ever.
TWRP installation took me two days. First, the computer (Win 7 32-bit) refused to recognize the TF300T and 'fastboot' could have been renamed 'nerverboot'. Strangely, the whole business seemed to evolve over time. Persistence was the name of the game - trying different USB ports, booting and rebooting (both tab and desktop). Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Code:
fastboot devices
returned '???????????????' over and over again. By uplugging/plugging the cable into the tablet a few times I suddenly got a nice long string of letters and numbers. It came and went a few times but after a while seemed to stabilize till I felt ready for the big push of TWRP. I got so many error messages: 'can't find twrp.img' (I'd renamed it); 'can't open twrp.img'; 'insufficient memory', etc, etc.. Suddenly, it worked. It took just over eight seconds to download the 6.95MB. Booting into recovery was rather heart-stopping, but it came up a treat.
After that it was relatively simple to set up the TWRP (I found Djibe89's guide https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744 especially useful and there's a copy in the -djibe Transformer Pad TF300T pack v3' http://bit.ly/djibe-tf300t-v3.
Flashing KatKiss 7.1_TF300T_029, open_gapps-arm7.1-pico, and SuperSU-v2.82 from the microSD I'd copied them to went like a dream and before I knew it the old tab was humming with life once more. I'm a very happy chappy!
I have just two queries (so far ) 1. djibe89 mentions the file 'deviceID.apk' but Tim doesn't. Is it still necessary? I believe it's to keep Google happy, but I've no problems downloading from the Play Store, so I've not installed it as yet.
2) While installing the 'Battery Calibration' app it briefly stated that the tab wasn't rooted. I assume if I've achieved all the above, then it must be?
Now I'm going to play. No doubt I'll be back with a few more queries before too long!
Special thanks to ebonit for his help and support.
capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
Click to expand...
Click to collapse
hi ,
you said that you succeeded to unlock the tablet ?
how ?!
i tried with unlocker v7 and 8 , i got the network error.
my tf330t is on 4.2.1.
i try hard reset, nothing helped.
i changed the mb, succeeded to root with motochopper.
please , i need help.
thanks
mitomon said:
I tried with unlocker v7 and 8 , i got the network error. My tf330t is on 4.2.1.
Click to expand...
Click to collapse
To avoid any issues please reinstall your system by doing a Buster99 https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. Be sure you have the latest firmware "WW_epad-user-10.6.1.27.5"
After that delete your Google account. Then you may unlock your device with V7.
capelyddol said:
TWRP installation took me two days. Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Click to expand...
Click to collapse
Hope you have Kang TWRP now as required by Tim in post #1!
I'm sorry, but you never mentioned that you cannot access your Tablet via ADB. Therefore please note, the best ADB tool, every Android user may have on his PC, is "Minimal ADB & Fastboot" https://forum.xda-developers.com/showthread.php?t=2317790.
BTW, the answer to your first question is nope, you don't need it. The answer to your second one is yes the device is rooted. However check the update status of your SuperSU. Hope you did fresh download Rom, Apps and SuperSU via Tim's links in post #1 of the Nougatella thread?
I have installed Kang TWRP 2.8.7.2 as per Timduru's link. My tab was wiped before installation so all apps were fresh downloads. SuperSU was 'UPDATE-SuperSU-v2.82-20170528234214.zip' again, as per Timduru's link, as was the ROM ' KatKiss-7.1_TF300T_030.zip'. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
capelyddol said:
My tab was wiped before installation so all apps were fresh downloads. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
Click to expand...
Click to collapse
You are welcome! It's good to hear that you did such a good job. Using the thanks button is always greatly appreciated.
Please note, if you have any issues or you are changing the Android system, Format /data through Kang TWRP is always required. Format /data is more than wipe (you did wipe!) or factory reset. It takes up to 1 hour to be successfully. After that your system is really clean.
"Warning: formatting will remove what is stored in your internal storage, so store the rom /gapps/supersu zips onto an external storage (microSD, SD card..) or make sure you know how to push them back through adb." advised by Tim in post #1.
.
zeroiron said:
Hey guys!
i'm a bloody noob.
i never did something like unbricking my phone or wiping it or flashing it. It was my first time doing something like this because i just hate stock roms nowadays.
to unlocking the bootloader on my phone was no problem. but the problem was, that i updated my phone to adroid 11 and all the files i found in the past (half year ago) was for android 10, i think.
BUT I DIDN'T KNEW THAT BEFORE! I didn't knew that it would cause problems or that i had to be cautions about that.
Whatever. I tried to follow the instructions on this site: https://wiki.lineageos.org/devices/guacamole/upgrade
the twrp site i used was: https://eu.dl.twrp.me/guacamole/
Is the data "https://eu.dl.twrp.me/guacamole/twrp-3.6.0_11-0-guacamole.img.html" from 2021-11-22 know for adroid 11?
Because half year ago, i think, this all didn't work because there was no twrp for adroid 11 outside.
to be honest i don't know if i tried to install something else too in the past. i don't remember anymore.
I stuck half year ago on this bootloop problem. and i didn't worked again on this phone. i thought i could just wait for a new data for android 11 and try it later again.
Later is today but i made i worse!
I downloaded from this site https://download.lineageos.org/guacamole the file:
lineage-18.1-20220227-recovery-guacamole.img
after the command 'fastboot flash boot xxx.img' i reboot my phone.
Now my phone is displaying :
qualcomm crashdump mode
dm-verity device corrupted force dump
kernel-restart
what can i do now?
If i press the sound buttons + off-button i come the the boot screen which says:
blablabla
internetsite
press power button to pause boot
but this display won't stay long enough. after few seconds it's again on this crashdump mode
edit: i think i wiped in the past the whole os. And now? What should i do?
On this MSM Tool my phone isn't recognized. even with newest driver or other cable.
What should i do know? Is my phone lost now?
If some can help me please write exactly down what i should click / download etc.
If someone can german here and knows help, please help me in german. but don't have to. i'm glad if anyone can help me.
Click to expand...
Click to collapse
From what I can gather from your details I would try to get the MSM tool to work, it sounds like a driver issue, just make sure you uninstall previous driver first then go here
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
and get latest driver , follow all instructions,, also make sure your PC is installing all the optional drivers in the windows update section while your phone is connected to the PC, hth,, good luck