I have googled the topic extensively but I could not get the proper answer till now.
My problem is I just wanted to root the my Nexus S, the instructions from the forum seemed easy. Reading about different methods, i went with the Superboot one, after preforming the task and everything seemed well what the terminal (mac) output meant. After it restarted it never rebooted the UI and just stuck with the boot screen ( Google written in the middle and a lock sign on the bottom).
I'm not pro with android since I only got the phone a few days ago, after more than a decade on simbian.
Anyway does anyone know what happend? Even better how to fix it? Flash the Rom?
Answer
I figured it out made, got a new version of Superboot and redid it and it works now.
Related
I originally purchased a GTablet from the original Woot! sale based on reviews during that sale that this was a wonderful tablet once a new rom was installed. The first tablet I purchased as a gift for my wife. I received it on a Friday after I got off work. Within about an hour, I was up and running with TNT Lite, a fully functional app market and Adobe Flash Player.
I primarily followed this guide from these forums. I had zero problems and everything worked flawlessly following the guide.
I was so impressed with the tablet, when it came up on Woot! again, I decided to purchase another one. This tablet arrived quickly, and by all appearances was the same as the tablet for my wife. I checked the stock OS, installed the OTA update and verified I was on 1.1 3588. I proceeded to follow the guide again and ran into problems immediately with the app market.
I used the basic app market fix listed and no matter how many times I did it, I couldn't see the majority of apps. I then began looking around the forums and found this guide for the titanium backup method. I followed this exactly and still the market wouldn't work.
I found one more guide (can't find the link now) that instructed me to edit files on the tablet to known working configurations. I grabbed the files and they already had exactly what the guide was telling me to change to. So no luck there.
I then remembered reading that some Roms had a working app market out of the box. I figured I'd try VEGAn or Cyanogen Rom instead of TNT Lite to see if this fixed this problem. This is when I ran into another brick wall. I was completely unable to load these Roms on my tablet. After performing the install in ClockWork Mod and rebooting, the tablet would get the ViewSonic screen with Birds and never complete the boot. I left it on that screen for as long as an hour and still nothing worked.
I came back to the forums looking for more information. Buried deep in the VEGAn 7.0 thread I found a gem from someone who had a similar boot problem (they made no mention of market problems). This person said they were able to fix the boot problems by using NVFlash to restore the tablet to original settings and pointed towards this thread as a possible fix.
I followed the steps in there directly. I was hung up for about 20 minutes trying to figure out how to use NVFlash and ClockWork mod until it dawned on me that accessing for NVFlash was used with the Volume Minus button instead of the Volume Plus button. So if you are confused in that section, keep in mind they use different power up methods and don't conflict.
After using NVFlash and restoring back to the original settings I was able to get into the stock rom. I tried the OTA update immediately and it failed after the download. Restarting the tablet fixed the problem. After you are able to boot back into the stock rom, I recommend a restart just in case. Then do the OTA 1.1 3588 update.
I then followed the original guide again. This time, everything worked as expected. Using TNTLite and the Market Fix worked the first time. I formatted and installed VEGAn and it worked on the first time too.
I decided to make this post as a thank you to everyone out there who works on these ROMs and everyone who has posted fixes to their problems. Hopefully this will help anyone else that is having problems.
My wife and I absolutely love our tablets and this wouldn't be possible without the fine people here.
TLDR;
Market was broken and known Market Fix didn't work. Used NVFlash and it fixed it.
NVFlash uses Volume Minus not Volume Plus
Restart Stock OS after first boot before installing OTA update
Thanks for posting this. I plan on switching to vegan from tnt lite soon. This is good info to know ahead of time.
Thanks for the info from someone who is waiting to theirs in the mail.
I got an issue trying to root my Droid 2 using SuperOneClick. as far as I can tell I have done everything needed to insure it is done correctly. Here's what usually happens, it will go to a step 7 and say reboot, and my phone will then reboot, or, it will say waiting on device and just stop. This occurs at step 5.
Also having same problem on my friend's Droid 2 with Gingerbread 2.3.4. Hoping for an update to this in this thread:
http://forum.xda-developers.com/showthread.php?t=1654368&highlight=2+3+4&page=2
Rooted many different phones before, but I've tried everything on this phone, but nothing works. I'm so frustrated. Apparently Motorola is doing everything in their power on OTA updates to prevent users from rooting! (or at least modifying something that requires a different exploit with each update). Watching tons of threads waiting for some breakthrough right now.....
Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!
Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good:
Ok first, I did a lot of research into the topic and spent more than a few months in thinking it over and seeing if I wanted to attempt this. In a day long research fest, I finally decided to just try rooting and installing my daily-driver Nexus 7 2013 Wi-Fi with CyanogenMod. I chose a method that wasn't too daunting, using the Nexus Root Tools to push the CM rom and finally into working... I used RootJunkie on YouTube, "How to Flash a rom with the Nexus Root Tool Kit plus make a Backup with one click" as a refrence, watchign and rewatching the video and all he referenced over and over.
I loaded the zips into the "Flash Zips" section (It loaded the GApps zip in first and then the CM image). It seemed to install without a hitch except the GApps weren't there. Figuring that it installed the GApps first and then wiped them, I redid the flash with the CM first and the GApps second. Now I'm stuck in the Cyanogenmod loading screen. Problem is, since it's hit the point where it installed everything and hasn't let me into the device, I haven't been able to enable USB debugging. Now the computer isn't able to recognize the device at all and I cannot push just the CM image to fix it nor can I restore factory since the computer doesn't recognize it.
I've attempted to boot into recovery mode, which just results in the android laying on its back with a red ! in a triangle over it. I'm sorry if this makes no sense but I'm slightly panicked because I can't afford to have this thing professionally fixed nor replace it at the moment and I use this tablet daily. Is there something I'm missing? I'm going to lay down for now and try to calm myself, letting the thing sit at the loading screen, hoping that it'll let me in after a while. What options do I have, I'm sorry if this is the wrong place, the wrong crowd... I've just browsed quietly and used XDA as my source for information for everything from rootig my first device to this and it seems I've overstepped my abilities in this.
Problem solved
I stepped away from my computer and tablet for an hour or two to calm down from a panic I was in and found that it let me into the bootloader finally where I flashed the stock image and then restarted the process.
I discovered my problem in trying to use the 'stock' level of GApps from opengapps when the Cyanogenmod wiki pointed directly for the 'nano' version. Sorting out a silly wizard crash later and my tablet is happy, healthy and working much better than the stock at the moment aside some setup I need to do.
Thread closed as OP solved his issue
Hey Folks,
got some messy Prob's with my old nVidia Shield LTE Tablet.
The Facts:
-KillSwitch not Triggered and it was succesfully Rooted in November 2015, TEGRA-OTA was also Removed (nomoreota)
-worked for Months (beneath one year), only Super-SU penetrated me periodely that it needs to be Updated, but it couldnt be done, it said "not enough Space" after trying to install a newer Version. :silly:
-past Month (January 2017) i decided to do a Factory-Reset, because Girlfriend should get the Shield, thats where the Problem started:
After clicking Factory-Reset, it began to work. After 4 Hours and nothing happening, i decided to Power it Off and start fresh with Installing a clean Stock-ROM and remove the TEGRA-OTA as i done a year before.
But from now on things get messy and to complicated for me.
In the Past i rooted and flashed it with "Shield-RAM", found here on xda.
But this Time it didnt ended with a working Shielt-Tablet. It stucks alwas in a Bootloop, in Recoverymode also as in normally booting the flashed OS.
Confused an disturbed by this, i tried different Recoverys (TWRP 2.8 and 3.0, also a CWM), all with the same Effect: Bootloop
Now i only can acces the Bootmenue which says Bootloader Unlocked.
I dont now what to do from here on and would be very happy and glad, if someone can help me figuring out whats going wrong.
If further Details are needed i will do my best to provide things i forgot here to mention.
With kind regards - ToxicFighter1
Ps.: excusy my bad spelling, bit rusty in flawless english typing:good:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Thanks, but that's not the problem. If I boot into Fastboot / Bootloader, it's totally fine. In fact, I can plug the tablet up to my PC when it's in any state and doesn't experience the issue. It only occurs when I have it plugged into AC. SO far, I've tried 3-4 different cables and power supplies for 2.4A, 2.1A, and 1.2A - all adapters which worked 100% prior to updating.
Suggestions?
OK - Finally fixed it...
I replaced everything as shown above, but ran into the issue again as soon as FlashFire installed the OTA. So, I tried a different way to upgrade and no longer have the issue. Below is what I did...
- Installed 4.4.0 via ADB/fastboot wirhOEM recovery
- Completed initial setup and upgraded to 5.0 via built in system update
- Rebooted
- Booted to bootloader and flashed TWRP recovery
- Booted to TWRP
- Installed SuperSU via sideload
I would have started out applying 5.0 via adb/fastboot, but have yet to see a full image available yet. Used same TWRP and SuperSU as originally used. Just eliminated GlashFire from process. Once I rebooted and everything loaded, plugged into 2.4a power, and it worked without going into boot loop.
Hope this may help someone else - Thanks
Hey Folks,
thx for the few answers, i'll try these Tips out the upcomig Days.
Lot'a Stuff to do atm, bit Busy.
With kind regards - Toxic
xanthrax said:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Click to expand...
Click to collapse
Hey there, and personally Thx for the provided Link.
As announced i did try it, but with no Success.
I'll or explicit the Tablet gets Stuck at Step 17, the Bootsreen doesn't disapear.
Dont know whats Wrong, cause i did all as menitioned in the Post, every ADB/Fastbootstep with Succes-Message, and because Bootloader was already Unlocked, i took the Rooted Image.
But now, im still on Bootscreen, sick
With kind regards!