I've been stuck in a boot loop on one of my G-Tabs for about 4 days now. Been trying every fix I can find to no avail so far. I have the Viewsonic to G-Tablet boot loop. I keep noticing people reffering to using NVFlash with the Img9 fix to add in ClockWord mod. Many said to do that flash then to wipe the data, which is where the problem lies. I get this error everytime I try:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
Repartition 2048 and 0.
Hello KJ and thanks for replying, I have seen you offer help to alot of people so thanks for dropping by here too.
I have tried that as well and it hasn't done anything. I don't know if it is the order in which I am doing things or what on this tab. My other one works like a dream but it was done before the 4539 (I think that's right) update came out.
I have done the NV Flash and added CWM via Ext SD and then partitioned and that was a no go. I also tried doing Roebeet's example of doing NVFlash and changing te Img9 file as well with a repart and that didn't work either.
I also tried this "fix" and even it didn't work.
http://forum.xda-developers.com/showthread.php?t=974422
I'm not giving up because from all I am reading, these things seem immpossible to fully brick. I also feel pretty safe to say that it is my fault and that maybe I don't have the correct order for doing the entire process but I have tried until I turned blue in the face before giving up and going to bed.
Well... what your tablet is having trouble mounting is the partitions that you should be creating with the repartitioning. /dev/blk/mmcblk3 is the internal memory. Are you familiar with ADB?
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Congrats, man. I think you're the first to truly brick his gtab.
tunez23 said:
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Click to expand...
Click to collapse
Unfortunately, I'm not a good enough teacher (I lack the proper patience) to get someone going with ADB from scratch. Especially since my development environment is somewhat unusual so I often have no frame of reference to assist in setting up the tools. So, if you're up to it, you need to do one of two things. Either get ADB installed and running on your computer or get a rooted ROM and a terminal emulator on the device that we need to work on.
Your situation is somewhat different from the others in that you can actually get CWM installed and get into recovery. I still think that perhaps some combination of partitioning, data wipe and fix permissions should be working for you. What I would do in your case is:
1) Data wipe one more time (perhaps use: http://forum.xda-developers.com/showthread.php?t=1030915)
2) Reboot into CWM recovery and repartition
3) nvflash the stock ROM again (without CWM)
4) Factory reset from the ROM settings
If that fails then research setting up ADB for your computer and we'll discuss some diagnostics you can run from that.
Thanks KJ, I will try those when I get home this evening.
Related
Hi All,
I've been reading this forum for a good few days now as I am trying to get my Kyros functioning the way I need it to. However, I've run into a few problems and am not 100% sure as to what to do. Before I go on, I'm not very techy, so I would be very greatful if replies could be as straight forward as possible, without much jargon as that really loses me
First off, we've just managed to install the windows and ADB drives. I'm following all the instructions from here: http://forum.xda-developers.com/showthread.php?t=858952. That took some hacks our side, but is now working.
I'm pretty stuck on the clockwork reboot though. Again, followed the instructions from the link above. When it initially rebooted, it went straight into the Android System Recovery mode (the robot with the triangle opening screen.) I've tried it over and over, following the directions exactly as explained in the link, but all I'm getting is the generic Androis system recov.
The Recovery zip file is on my SD card. Do I need to unzip it to get the recovery.img to show? Is that something that I'm doing wrong? I also updated the OS (I guess) from the coby site before I started working on these other changes.
So basically, this is the issue right now. Trying to get the clockwork to run and all I'm getting is the android system...and that's when it doesn't just reboot back to the home screen directly.
Any advice would be great. Thanks
And out of the blue, after an hour of angry TV watching, it's now worked. I can't tell you what I did differently as I followed all the same steps as before. Must just have been lucky I guess.
I am having the same issue, and i tried to unzip the update.zip but i boot back to the recovery mode, can someone assist me with this, i have a galaxy s (Vibrant).
thanks
Try going to your sd folder and delete the clockwork recovery folder then uninstall rom manager and redownload it from the market after it installs open up rom manager and click on flash clockworkmod recovery and let it download the update.zip file and your done
Sent from my SGH-T959 using XDA App
Oh yeah after all those steps and you still get back into the stock recovery system click on reinstall package and it should boot into cwm I hope that helps
Sent from my SGH-T959 using XDA App
ASR
baalcat said:
Trying to get the clockwork to run and all I'm getting is the android system
Click to expand...
Click to collapse
like this ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess you'll find out shortly cause i'm about to do it
Factory reset should not touch /system which is where the binary and apk reside.
Sent from my MB865
Well, here are some preliminary findings
After rooting I was not able to use my phone for USB Mass storage, not exactly sure why, just an observation. Before root, it worked fine.
After FR, I am now able to use my phone for USB MS again. However, upon the first time trying to mount it as MS device I got a pop up window telling me of one or more problems on the disk (sdcard) and it said that happens when a file or files were not done writing to the card before it was unmounted. Not sure how that could have happened, but it did. It gave me two options, scan and fix Atrix 2 or scan w/o fixing Atrix 2. Choosing option 1 would run checkdisc and attempt to fix any problems found, that's what I did and it fixed the problem.
After rooting I was unable to check for system updates, let me clarify....I could physically tell the phone to check for them but I would get an error that said "Check for system update is not available at this time, please try again later."
After FR, I get a different message that states "Your device is up to date, no update necessary at this time."
After rooting I was able to use MyBackup Root to backup all my apps and stuff.
After FR, this is what I get when trying to open the app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am going to install SU to see if that changes anything re: root access, will post back with update.
i launched Titanium Backup the other day after rebooting and it said i didnt have root. rebooted again and launched the app, root came back....its really weird... had this happen on the Atrix 1 as well. even on custom roms that are pre-rooted.
A lot of times it is because the superuser app is not running or failed to launch. Opening superuser and going back to whatever app complained usually works for me.
IMO, I haven't even rooted this device (yet) but that's my experience on my last phone.
koriflame said:
A lot of times it is because the superuser app is not running or failed to launch. Opening superuser and going back to whatever app complained usually works for me.
IMO, I haven't even rooted this device (yet) but that's my experience on my last phone.
Click to expand...
Click to collapse
out of all the devices i have and have had, the atrix and the atrix 2 are the only ones i have seen this on.
It's worth a try, next time it occurs. Again, I haven't done anything with this device specifically, so it could be something else.
I've decided not to try it, nothing really to gain at this point since rooting this phone doesn't accomplish much yet.
Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Major kudos to diego930 for such a nicely detailed description of his problem!
Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.
Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!
When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.
ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.
Hi everyone. Please bear with me I am a complete noob at this stuff.
I have a HTC one sv c525e K2_ul 4.2.2 S-on in Aus with optus (maybe LTE??)
The storage space for apps is tiny so I wanted to root the phone to re-compartment space.
I eventually found and followed the tutorial by qbking77 to unlock the phone and root it. I did well up until entering recovery to root the phone. The twrp image I used didn't work on my phone. I tried several of them with same result. Somewhere along the line I got the bootloop. I don't recall if it was before or after I tried to flash this I think I tried some other kernel that I can't find now.
Anyway I went back to twrp and tried more images. One finally worked to get into recovery. It was- twrp-2.8.6.0-k2_cl.img 10.4M the second listing under HTC One SV Boost USA (k2_cl).
So now I could enter recovery mode I went back to qbking77's tutorial. I found the options and process on my phone was different to his and I had a few errors come up like unable to mount sdcard, storage and some other stuff. As a result I was unable to do a back up and unable to install super user. From there I still got the bootloop.
Although internal sdcard and storage was unable to mount the phone did see the external sd card. So I loaded the super user zip direct from pc to sd card and opened the zip in recovery. Still bootloop.
I was wondering if I managed to unwittingly delete some important ****. So in my brilliance to persevere with screwing with it, I loaded the venom ROM (and some kernel) onto the ext sd card and opened it in recovery. Still several errors came up and I wasn't given any options to pick before flashing. It did say installation was a success at the end. Still got bootloop.
So I am hoping someone might see an obvious f-up that would turn into an easy fix ......... :laugh:
So I've been doing some reading :angel: but I'm no better off. I watched closely what I was doing and I was getting an MD5 error. I tried downloading the zips in firefox so as not to corrupt them but the phone is still coming up with 'missing MD5'.
I'm thinking my only option at this point is to run the RUU as I've seen that suggested a few times to others. Looks like a PITA but I guess it's that or new phone
I don't know when I'll get around to doing it.
Looking into RUU I need the S-off. Since I can't boot the system does anyone know how I can switch the S to off through fastboot or recovery?
So I was too lazy to run the RUU. I again attempted to flash the viper ROM. In recovery it says it was a success but I still get the bootloop. I noticed when I went into recovery something would flash up on the screen but it was too quick for me to read so I took a picture of it. Does anyone know what any of it means?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys! i have an issue here. can anyone help me solve this problem.
before i started getting this error i had, they were working well
- AOKP 4.4.4 custom rom
- Philz touch 6.0 Recovery.
from few days i started getting this error, see image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash stock firmware, i downloaded two firmware of INU region (India)
everytime i get the following error on odin,
(Above pic for reference only. im using odin v3.09 and latest)
I tried flashing with PIT files, it didnt work.
I tried flashing TWRP, CWM it flashes recovery but when i go to recovery then still philz is there.
I searched on many forums and Googled, and i came to know that my /data and /sdcard is corrupted. but i can access the content /sdcard from recovery and i can view my files.
I tried flashing other custom rom. It flashes them without any error but when i reboot my Tab its not flashed. its same.
What to do please help me.
Ok so after doing so mush research on this on xda, gsm-hosting, google, etc....
i came to a conclusion that the emmc is corrupted or right protected (Means It has become read only). which is why we are unable to flash through odin or through recovery. even if the flash is successful then after reboot the TAB returns to the earlier state i.e same rom, bootloop and recovery.
so there are three way you can fix it:
1. change motherboard, which is very costly. on ebay it was 13k (India). dont know about local shops or service center. but im sure it will be more or less same.
2. Change emmc. ask the repair guy to change the buggy emmc to a new one. buy the emmc from alibaba online store or other online stores if you cant find it offline.
3. You can get back the same tab to work by directly flashing the stock rom directly to emmc. This process involves soldering the pins of the tab and flashing directly on to the chip using a box called ATF (Advance turbo flasher). This process is little advance, one can do it if you know what pins to solder (You can get the idea from youtube & gsm hosting), but buying atf box would be costly. costlier than the emmc replacement. now if you want to experiment and learn you can go buy a atf and revive your dead tab (it will be called The walking dead. ).
:)
so i am replying to my own thread so that if any body is comes searching for the same gets to know what happened and what to do next.
BTW Android_Andi has done some great research on this he tried every possible thing but unfortunately it didnt work. Thanks to him for his time and effort.
and if anybody figures out how to fix it without using atf box please do post and let me know. because im keeping my dead tab with me and if someone knows any alternate way i can fix mine too. who knows anything can happen.