its been weeks trying to figure why is still doing this, the problem is since the last time i updated CM9 it stared bootloop and then when i was to mount the tablet the computer didnt connect so what i did was i downloaded the universal Naked drivers twice and still no connect i am trying to update the CWM but i cant since it wont mount is there a way i can fix this? i would love to bring it back running need help !!!!
same thing here...CM9 causing CWM bootloops...WTF.
klutch said:
its been weeks trying to figure why is still doing this, the problem is since the last time i updated CM9 it stared bootloop and then when i was to mount the tablet the computer didnt connect so what i did was i downloaded the universal Naked drivers twice and still no connect i am trying to update the CWM but i cant since it wont mount is there a way i can fix this? i would love to bring it back running need help !!!!
Click to expand...
Click to collapse
i think you're going to need to use adb to push the rom files into your SD card
i believe the naked drivers are for adb
this is the command you're gonna need to use to push the files into your prime
Code:
adb push [insert rom here minus the bracket] /mnt/sdcard/
hope this helps~
i mean i know about the adb push but the problem is since that cause me some issues the CM9 nightlys it wont mount no mater wat i do wont mount
I deleted the external_sd folder with ES_fileexplorer, after that no app could recognize my usb_storrage.
Then I wanted to flash my galaxy note with Cyanogen again, but now CWM cant find the usb_storrage too.
I am also stuck @ CWM now :/
---------- Post added at 11:53 PM ---------- Previous post was at 11:21 PM ----------
smrtnik said:
I deleted the external_sd folder with ES_fileexplorer, after that no app could recognize my usb_storrage.
Then I wanted to flash my galaxy note with Cyanogen again, but now CWM cant find the usb_storrage too.
I am also stuck @ CWM now :/
Click to expand...
Click to collapse
Hmm seems like I formated my sd_card via CWM and CWM coldunt find any files ofc...now it works again. But unluckly it still can not find external_sd
klutch said:
i mean i know about the adb push but the problem is since that cause me some issues the CM9 nightlys it wont mount no mater wat i do wont mount
Click to expand...
Click to collapse
If you are trying to mount in cwm
I believe it's a known issue that doesn't work
so wat u trying to say that CM9 nitelys did the unknown issue?
klutch said:
its been weeks trying to figure why is still doing this, the problem is since the last time i updated CM9 it stared bootloop and then when i was to mount the tablet the computer didnt connect so what i did was i downloaded the universal Naked drivers twice and still no connect i am trying to update the CWM but i cant since it wont mount is there a way i can fix this? i would love to bring it back running need help !!!!
Click to expand...
Click to collapse
bro I was running the same CM9 and it screwed my Prime up like yours...CWM bootloop only...
my Prime was also not showing up when attached to the usb/computer...
after reading a bunch of very vague instructions and going through 5 or 6 different methods of trying to get it back I finally gave the following method a shot and it worked the first time (from the dev DiamondBack's thread)---
Code:
To recover your Prime (most likely) you need the following:
A working ADB setup (please google that if you don't have it, "tutorial setup adb" or something like that should do the trick)
The USB-Cable to connect the Prime to your PC
A few minutes time
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
[CODE]Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
[/CODE]
this guy saved my panicked ass....thought my Prime was done...but these instructions brought it back...
well @ least u got urs running but i am still stuck wondering why i cant mount and the drivers are downloaded right i still dont get it i tried so many things and i went to W-XP and no luck @ all no i am scared that its bricked or something n spend 500 on a tablet n now wont work
I'm having the exact same issue, tried out CM9 and it now bootloops my prime into cwm. windows can't see the prime either when I connect it, so adb doesn't work, so when I type "adb shell" it comes back with "error: device not found"
before this, I was having issues with my tfp being recognized by windows. this is on 2 diff desktops (win7 and xp) and my laptop which is win7.
well my friend welcome to the same boat i have that same exact issue
ugh... does this mean I have a paperweight now?
jackmei2 said:
ugh... does this mean I have a paperweight now?
Click to expand...
Click to collapse
i dont know bro lol but all i know i dont want to drain a 500 buck tablet on the train because its going to hurt
have you tried contacting Asus regarding this issue? I think I might try and RMA the unit and complain that it won't connect to the PC or charge directly from the wall plug.
i mean if not mistaking theres no point contacting Asus when is hacked and bootloader unlocked its out of warrenty
yeah..it warns you like two or three times that unlocking the bootloader voids the warranty...
i know one of you has...but has everyone tried the method posted on the first page that saved the other guy?
when you're bootlooping, if you hold down the volume and power button for 5-10 seconds to get to recovery, does it automatically bootloop or does the text appear and give you the option to press volume up?
i was bootlooping and holding vol down and power for a long period of time, then manually going into recovery worked...
or does everything bootloop?..meaning can't even get into the rom itself
i'm asking because you mention cwm bootloop... if you try to force recovery by the above mentioned method (holding vol down and power during the bootloops until you get the option to go into recovery...) then just not hit anything and let it try to boot normally...
i know i'm not giving breakthrough advice, but hopefully some of this will help..
I thought I've seen a few posts where people have sent their TFP in for service even after they've unlocked it... it can't hurt to call and see what they say.
when I turn on my TFP it automatically finds CWM and boots right into it without me being able to press up to confirm. I think CM9 did this when I tried to boot directly from CM9 into recovery. so actually, I'm not bootlooping, I can get into CWM, but I can't do much else from there, not even turn off my TFP... I always have to wait for it to run out of power before it shuts off.
nono not that way bro i mean it ok ... u turn it on it comes the asus screen after that it go to CWM and if i reboot it does the same thing so basicly its no moving from asus just back to CWM and like i said its not mounting dont know why i tried XP and W7 n nothing intalled driver n nothing
I called Asus, and you can send in your unlocked TFP for repair... but they won't say how much it would cost, even if it is a hardware issue, they will still charge you. freaking lame...
so basicly i am stuck with my TF201 n cant do nothing damn
Related
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
Can you still boot into your main ROM or not? IF so, just reinstall recovery - Clockwork Mod 0.8 works, I don't know about later versions or ROM Manager, I don't trust them, based on what I see on the forums.
If you can't boot into recovery OR boot normally, then you have to use APX mode and nvflash to reflash your G Tablet. That completely wipes and rewrites everything on the tablet.
EDIT: If indeed it sounds like clockwork isn't installed and stock recovery is still working, see the instructions in the next post to install clockwork mod 0.8. No need to resort to nvflash.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
You could become a professional gadget breaker with all the broken stuff you have
Clockwork never got installed if you are seeing the ! and then it reboots. I would not fool with rom manager, or any of the other stuff. Your tablet is NOT a Vega. The vega rom is used as a base to build stuff for the G tablet but it is not the same.
Get clockwork installed. You need to find Clockwork.8 ... You will have an update.zip file, and a recovery folder with a command file inside it. You can install it from the internal sdcard, or an external. You just need to look at the command file with a text editor like notepad and see if it lists sdcard, or sdcard2. If you want to install from internal, sdcard.. From external, sdcard2. The command file does not have an extension. If you do not have one in your clockwork package then download one of the other roms. Most of them will have it. Or even the stock rom package. They are all the same.
Go to SDX and we'll help you with the Intercept. Follow the info hear and the G will be rockin.
webosb said:
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
Click to expand...
Click to collapse
I'm pretty sure I wrote that... I don't care that your reposting it...just link where you got it from next time.
Anywho, keep in mind that it's nearly impossible to completely brick these things. Follow this guide, step by step, from start to finish. You will need a microSD card with a way to get files onto it (microSD slot on computer/SD slot with microSD -> SD adapter)
http://forum.xda-developers.com/showthread.php?t=865245
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
If you really have managed to mess up recovery.. You can use Nvflash to get all the way back to stock. Just use caution.. The only 2 tablets I know of that may have actually been completely bricked have been from folks that ran the incorrect batch file in Nvflash... It is really simple to use though... Guide is here...
http://forum.xda-developers.com/showthread.php?t=861950&highlight=nvflash
scsione889 said:
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
Click to expand...
Click to collapse
Yeah, I got it to recognize it, I didn't take recovery and update.zip out of the cwrecovery folder so it didn't work before. I just got it to "unpackage" for a second. but the same boot cycle happened.
I have to run out now for a bit, I'll try the flash later. Thanks for the help so far.
As mentioned before you need a microSD to put the CM recovery on. It also needs to be the .8version of clockwork. AndroidPolice is alright but you really should stick to the xda forums for this kinda thing. It only took me 5 mins to flash clockwork and get the VEGAn build up and running. I wish you the best of luck with your tab. It really is a nifty device....once you're running a custom ROM lol.
Edit: you can hard reset...unfortunately viewsonic failed to make a hole in the case to be able to reach it
Sent from my VEGAn G-Tab
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
Happy New Year! I hope!
Hello,
I flashed my GTab with TNT Lite a while back, but I was going to switch to Vegan. When I try to go into recovery mode, I get the message in the corner "Recovery Key Detected" but it won't go into CWM. I've got the update.zip and Recovery folder (with command file) in the root of my sdcard. I opened the command file to check the file path, and it's to the internal sdcard, not sdcard2. I even put those files on sdcard2 just in case, but still no go.
Any ideas? CWM 0.8 worked like a charm the first time around when I flashed to TNT Lite 4.2.1, but I just can't get into recovery anymore. I redownloaded it, and erased and put new versions of the update.zip and recovery folder on the sdcard (when the existing ones didn't work), just in case, but still no go.
I can still boot into my ROM, so I also tried "Reboot into recovery mode" from CWM inside the app, but it reboots to the Viewsonic splash screen and hangs there.
Any help would really be appreciated.
Hey, so I ran into the same problem as the first post (with the recycling boot screens). I flashed TNT-Lite onto it, and it worked for a few hours before the problem happened. I NVFlashed it, and at the very least I know the recovery screen is different than after I flashed it, but the yield sign only lasts a few seconds and then the problem persists.
Does NVFlash actually unroot? If so, can I return this to viewsonic and get a replacement? If not, am I screwed?
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
To NVFlash using windows 7 shouldn't be a problem I actually used it today and I'm running windows 7 home edition maybe you need to update your PC and try a linux live CD to run linux on a PC it has more drivers available for equipment and saves someone who doesn't understand linux alot of headache as it uses the CD as your hard disk and it sets it self up just make your system boot from the CD first.
Sent from my Bottle of Smoke using XDA Premium App
TimmSpinn said:
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
Click to expand...
Click to collapse
Really it depends on your boot loader branch and its good practice to ensure that everything installs as the Rom develoer intends.
Sent from my Bottle of Smoke using XDA Premium App
While I was checking my emails i rediscovered this thread... lol
I'm a linux user, I got ubuntu 10.10 on my laptop running, again, months ago.
But now I don't touch it and use my tablet or phone 98% of the time. (this is 2% other on an XP desktop)
I also share the same recovery mode issues, but after reading the rest of this topic, I think I might feel adventurous enough to try that honeycomb... >.>
stuck cant get into cwm and is stuck on the tapntap logo
after i nvflash the tablet it wont boot. it gets stuck on the tapntap logo after a few seconds it turns the screen black. and even cant get into cwn it just get stuck on the view sonic logo. i need help
i have a gtab and it is giving me a headache already trying to figure out how to fix it. I have search high andd low for a solution but havent quite found one, yet.
This is my brother-in-laws gtab. For some reason he tried to flash to a different rom and update the tablet. Right now, the tablet won't boot. It gets stuck on the 3 bird screen. If i try to go into recovery, i still get the 3 birds with the "detected a recovery key pressed."
What i have done...well since i can get into apx mode, the first thing i did was flash nvflash 1.1, that should clear things up, then i pushed recovery. But that didn't work, i am still at the same place i started. So i flashed nvflash 1.2, still didn't work. I re-downloaded the files again from different sources and tried it again, and again, and again. I have tried it atleast 6 times but all with the same outcome. I am still stuck at the 3 birds. I tried holding the + while in nvflash to boot into recovery but that didn't work either. I am fresh out of ideas. Everything i read tells me to wipe cache/data, but i can't even get into CW. And nvflash isn't working for me either.
I am still on the same screen, this darn gtab is giving me the bird three times over. so right now i am going to allow the battery to drain then try again. unless anyone can suggest anything that will give me some hope....or even to tell me that i have bricked the "unbrickable."
oh and everytime i do the nvflash the device does not reboot itself...it stays stuck on the "entering nvflash recovery mode / nv3p server"
I had a similar issue with my gtab except I keptrebooting into apx mode. I then downloaded some nvflash from roebert that said deprecated not use (in a dropbox) and flashed that, my gtab came back to life there... funny thing is that I'm pretty sure I ended up on 1.0, luckily I was able to flash came from that and it's all been good from there.
I would say give that a try, then again I'm relatively proud to say I'm a n00b at Modding these things so tread carefully.
PS : as unbrickable as the gtab might or might not be it can (and to me it is) quite frustrating ; so I feel your pain
rantsh said:
I had a similar issue with my gtab except I keptrebooting into apx mode. I then downloaded some nvflash from roebert that said deprecated not use (in a dropbox) and flashed that, my gtab came back to life there... funny thing is that I'm pretty sure I ended up on 1.0, luckily I was able to flash came from that and it's all been good from there.
I would say give that a try, then again I'm relatively proud to say I'm a n00b at Modding these things so tread carefully.
PS : as unbrickable as the gtab might or might not be it can (and to me it is) quite frustrating ; so I feel your pain
Click to expand...
Click to collapse
yeah i tried it...i wish it was that easy..but it didn't work..it still didn't do a reboot after nvflash, and when i powered it off i didn't get anything...
butwhydoitalk2u said:
i have a gtab and it is giving me a headache already trying to figure out how to fix it. I have search high andd low for a solution but havent quite found one, yet.
This is my brother-in-laws gtab. For some reason he tried to flash to a different rom and update the tablet. Right now, the tablet won't boot. It gets stuck on the 3 bird screen. If i try to go into recovery, i still get the 3 birds with the "detected a recovery key pressed."
What i have done...well since i can get into apx mode, the first thing i did was flash nvflash 1.1, that should clear things up, then i pushed recovery. But that didn't work, i am still at the same place i started. So i flashed nvflash 1.2, still didn't work. I re-downloaded the files again from different sources and tried it again, and again, and again. I have tried it atleast 6 times but all with the same outcome. I am still stuck at the 3 birds. I tried holding the + while in nvflash to boot into recovery but that didn't work either. I am fresh out of ideas. Everything i read tells me to wipe cache/data, but i can't even get into CW. And nvflash isn't working for me either.
I am still on the same screen, this darn gtab is giving me the bird three times over. so right now i am going to allow the battery to drain then try again. unless anyone can suggest anything that will give me some hope....or even to tell me that i have bricked the "unbrickable."
oh and everytime i do the nvflash the device does not reboot itself...it stays stuck on the "entering nvflash recovery mode / nv3p server"
Click to expand...
Click to collapse
www.viewsonic-gtablet-for-dummies.webs.com/
You're a code red. You've been missing a very important step. Please follow instructions precisely.
goodintentions said:
www.viewsonic-gtablet-for-dummies.webs.com/
You're a code red. You've been missing a very important step. Please follow instructions precisely.
Click to expand...
Click to collapse
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. either way, after i flash nvflash the tablet does not reboot it stays at the nv3p server screen. If i turn it off and back on again the birds come out again. i have even held to the volume + during nvflash and it shows the nv3p server, detect a recovery key pressed, and booting recovery kernel, but no go...it's just stuck...i can turn it on and off, i can get it in and out of apx but it will not reboot after nvflash or boot up a rom or clockwork recovery.
btw, i do have my own tablet as well and i ran nvflash on it just for giggles, and it works as it is suppose to. After it flashes it boots up to tap n
butwhydoitalk2u said:
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. either way, after i flash nvflash the tablet does not reboot it stays at the nv3p server screen. If i turn it off and back on again the birds come out again. i have even held to the volume + during nvflash and it shows the nv3p server, detect a recovery key pressed, and booting recovery kernel, but no go...it's just stuck...i can turn it on and off, i can get it in and out of apx but it will not reboot after nvflash or boot up a rom or clockwork recovery.
btw, i do have my own tablet as well and i ran nvflash on it just for giggles, and it works as it is suppose to. After it flashes it boots up to tap n
Click to expand...
Click to collapse
Try code detox, you need a pc/laptop and load the proper driver, run the bat file from the directory. This mode completely reload all the petitions and usually fixes the issue. I think your boot petition is toasted.
Good luck.
tsukaza said:
Try code detox, you need a pc/laptop and load the proper driver, run the bat file from the directory. This mode completely reload all the petitions and usually fixes the issue. I think your boot petition is toasted.
Good luck.
Click to expand...
Click to collapse
This is not normal...
I did the detox and i DID get the "magic value mismatch" in the apx mode. But then i loaded the nvflash it is still in the same state as it was before...not loading recovery, booting, i can only get into apx mode...this is really weird..
I did the detox with both nvflash, 1.1 & 1.2, with and without Clockwork, but none worked. I can do the nvflash "format" and i still get the mismatch message but redoing the nvflash to get the tap n tap stock image or heck even not seeing the darn birds it won't do...
I have even taken it apart, let the battery run out, pulled the battery, pressed the reset button...but nothing!
I can't push anything in adb since i can't boot or get into clockwork...i think the tablet is offically bricked...i have ran out of ideas and have read many...i
butwhydoitalk2u said:
I have done every step on both code red and code double red...code triple doesn't apply since i can still get into apx mode. . .
Click to expand...
Click to collapse
Give this one a try and let us know if it helps.
Dave,
mydave1 said:
Give this one a try and let us know if it helps.
Dave,
Click to expand...
Click to collapse
I just tried ... and no cigar... i can go all the way to step 2.1 but it won't boot to recovery...it stays at the apx "entering nvflash...recovery key detected...booting recovery..."
to me it seems like it is not retaining any of the info that i am pushing onto it...like a "bios" is being reset and not remembering what to do...
A new error message.
Sent from my PC36100 using Tapatalk
Edit: i reflashed nvflash 1.2 and got rid of the error message...but i am back at square one...but taking a look at the error and from what i am seeing the tab is not finding the kernel image to start recovery. but why?
Cannot get NVFlash to "take"
butwhydoitalk2u said:
A new error message.
Sent from my PC36100 using Tapatalk
Edit: i reflashed nvflash 1.2 and got rid of the error message...but i am back at square one...but taking a look at the error and from what i am seeing the tab is not finding the kernel image to start recovery. but why?
Click to expand...
Click to collapse
Did you (or anyone else) discover the "secret" here? What did you do?
Unfortunately, I am now experiencing EXACTLY the same issues. My processes have fixed tons of GTabs that people thought were bricked. I *THOUGHT* that there was no way to HARD-brick the device but I may have been wrong!
I really need some help here. Anyone have an answer?
You could install a copy of Ubuntu and try nvflash with that. That would eliminate any possible driver issues since Ubuntu does not require drivers for apx mode. From the error you posted earlier "entering nvflash recovery mode / nv3p server" it would appear nvflash is not actually flashing anything.
Sent from my Nexus S using XDA App
NVFlash does not "take"
the3dman said:
You could install a copy of Ubuntu and try nvflash with that. That would eliminate any possible driver issues since Ubuntu does not require drivers for apx mode. From the error you posted earlier "entering nvflash recovery mode / nv3p server" it would appear nvflash is not actually flashing anything.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thanks for the comment. I agree about Ubuntu. I use it exclusively - have for a couple years. I did all my testing and attempts with it. I finally decided to build a WinXP machine and I am now trying to use it.
You are correct about NVFlash not saving anything to the device. There is no bootloader and although all of the NVFlash commands are "successful" it just does not save.
When I try to use the external SDCard to run recovery, the GTab does not seem to recognize it. It acts just as if there was not a recovery file on the card.
One thing that seems to give me some hope. I am seeing the USB connection (while not in APX mode) with the Windows Machine. So, I will install ADB and see if I can grab control that way. But ADB is such a bugger with Windows.
This thread is referring to this method of unbricking:
http://forum.xda-developers.com/showthread.php?t=1226470
I am having the same issue from the OP. However, when I get to step 3-5 where I use "adb reboot bootloader", it doesn't bring me to the bootloader (blue screen). At first when I tried to time it right, I got "device not found". However, as I tried more often, the command seems to go through as it returns blank, but the only thing that happens is the phone reboots and displays the "factory reset...formatting data...formatting cache...do not remove batttery...rebooting" again.
I've tried about 20 times now and, instead of bringing me to the bootloader screen, it keeps rebooting everytime I use "adb reboot bootloader. I would appreciate any help I can get.
I started a new thread because I cannot reply to the original thread as I do not have 10+ posts yet
I was thinking maybe I can't boot into bootloader since it cant even boot into recovery? Is that possible?
I'm in the exact same boat as the OP.
qmriis said:
I'm in the exact same boat as the OP.
Click to expand...
Click to collapse
well guys you are not alone :crying: i was try to fix my wife phone today and i have the same loop issue like OP. the hard part is the windows won't reconize the phone anymore just for a instance of sec when phone start the format processes t clear format and install and boot at the same screen over and over so way i can get to fastboot or even recovery mode
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
jmserapion said:
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
Click to expand...
Click to collapse
First off are you rooted? Do you have a custom recovery installed? Are you running a custom ROM or kernel? If you you have a custom recovery did you make a backup? If you can provide some more details I can try to help you out.
Sent from my SCH-I535 using xda premium
Alcatel OT5020t - Mediatek BOOTLOOP SOLVED!!
jmserapion said:
it charges and when i try to turn it on, it just get stuck on bootloop. I tried the hard reset, it doesn't work. im so frustrated. please help!
Click to expand...
Click to collapse
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Pop c7 7041x
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
I have 7041x stuck in boot loop. Flashing a rom by CVM doesnt even help. Could you please tell us how you fixed yours.?
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
hello,
can anyone help me please ? i have flashed my alcatel one touch fierce 2 7040n with the wrong flash, now it's stuck in bootloop i have just access to recovery mode so i tried wipe data/factory reset and wipe cache partition but there's no change. then i installed adb and all usb drivers on my pc and tried to send the zip package with adb sideload but it dosen't work. so i tried my last chance to update from sd card, i put the zip file package in the root of a formatted sd card, the phone detect the sd card and mount it correctly but the files was not showing (just like it's empty) i don't know why, is there any solution for that issue ?
i really need your help and thank you in advance.
nabil_rachak said:
hello,
can anyone help me please ? i have flashed my alcatel one touch fierce 2 7040n with the wrong flash, now it's stuck in bootloop i have just access to recovery mode so i tried wipe data/factory reset and wipe cache partition but there's no change. then i installed adb and all usb drivers on my pc and tried to send the zip package with adb sideload but it dosen't work. so i tried my last chance to update from sd card, i put the zip file package in the root of a formatted sd card, the phone detect the sd card and mount it correctly but the files was not showing (just like it's empty) i don't know why, is there any solution for that issue ?
i really need your help and thank you in advance.
Click to expand...
Click to collapse
It's been so long since i messed with these Alcatel phones. But if i recall, you can take the rom zip or update zip, and you have to rename it to some special name. Then you put it on sd card and it'll install to phone.
But in your case, if you flashed wrong. There might be something else.
But either way. Since you can boot into recovery or bootloader you should be able to push stock firmware to device. You need to make sure you get the correct files for your device.
This is most i can tell you. I've been using samsung devices for past years and forgot alot about flashing devices such as this through adb.
All i can say is, at least it doesn't seem like your hard bricked. As long as you can get into bootloader mode or recovery, you should have a way to fix. Search and Google around! Good luck!
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
Whenever learning to mess with phones and roms with adb and fast boot. As a lot of devices are different, but some simple key facts to follow are as follows.
Find out your devices partition layout (which partition is boot, system, recovery)
Don't mess with any other partition but them.
Always, always make a backup of all partitions with 'dd' command. And keep safe.
Need build prop
aaron74 said:
I know this thread is old but I suffered from this too and studied the web for days, tried mtk tools, sp tools, adb sideload. Nothing worked. Well, after days of fiddleing I figured out how to get ADB shell to work. Now in my case i knew i had a bad build.prop. So i knew what to replace.
Instead of holding 'vol-up' + 'pwr' buttons for recovery, Hold 'vol-dwn' + 'pwr' butons til it starts. my screen stayed on the one touch logo screen. It must boot up into the preloader. I was then able to run proper adb commands to replace my build.prop.
Hope this helps anyone that stumples across this. cause i know how frustrating it is to spend countless hours on a problem and get no where. If i can help, Reply to this.
If this helps, Please click Thanks!
edit- Let me say this only allows you to fix files you might have messed up editing. This will not allow you to recover from flashing a bad Recovery, as far as i know.
Click to expand...
Click to collapse
Where would I find the build prop bro? Thx
I was on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.