• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] Bootloop on victorious install and the new kernel

you should take your sd card out, use your pc card reader, download goldmans stock rooted backup, recover it, and flash victorouis, if it don't work, then ask jerryscript for help, hes a genius and got my phone running when I flashed victorious and deleted ghe system because I had a frozen screen from some app, and right now I have the same thing uggh, I hate bootllops and boot freezes, I just want to throw my phone to the garbage sometimes, and it happens when I feel the power of 1.7ghz
 
Are you wiping anything other than cache and dalvik cache when flashing Victorious?

Wiping data can bootloop youe, wiping system WILL bootloop you.

You are using a VirginMobile phone and not a Sprint phone right (just checking)?
 
Oddly enough I have the same issue as well. I updated from 0.2.1 while wiping cache and dalvik cache before flashing. I have no idea what's causing the loop.
 
Hopefully you followed instructions and did a backup before flashing. If so, restore it, or if not, flash a previous build and let me know what happens.

Be sure you have the Victorious-0.2.2-r1 zip file!

Did either of you update your SuperUser before updating?

If you are willing to flash 0.2.2-r1 again and have adb installed, please pull a logcat and post it to pastebin so we can see what's happening.

Steps to logcat:

  1. Make sure you have the Samsung drivers working on your PC
  2. Download this View attachment ADB-Victory.zip (for Windows only, Linux see below) and unzip it
  3. Open a command prompt in that folder (or open one and cd to it)
  4. Turn off your phone, plug it into your computer, then turn it on
  5. Wait till you see the bootanimation begin
  6. Type in
    Code: 
    adb logcat > logcat.txt
  7. Wait 60 seconds then press cntrl+c to stop logcat
  8. Copy the contents of logcat.txt in that folder to pastebin.com
  9. Post the URL from pastbin here for us to view
  10. Thanks for helping debug the issue!

If you have no output in logcat.txt, try again, but this time run this command:
Code: 
adb logcat >> logcat.txt
Wait 15 seconds, then press cntrl+c and the immediately press the up arrow then enter. Repeat with cntrl+c then up arrow then enter 4 or 5 times. If your computer was able to connect to the phone at any point, you should have lots of lines in logcat.txt


Linux users, download the Android SDK and follow it's instrutions to get ADB working.
 
jerryscript I cannot find the backups in twrp when I put them in that part of my sdcard, I need help, and yes I used external storage
 
First GO Into TWRP
Make a backup of only your Cache
Delete That Backup
Take out your sd card and plug it into your computer
Look for a "TWRP" open it up
Go into all the folders until you cannot any more
Paste your backups
Plug it back into your phone
boot up TWRP
And Enjoy Your Restore! :)
 
I just flashed the overclocked gpu kernel with no issues i wiped cache and dalvik cause i always do and flashed
 
I might just restore to my complete stock backup and try the ROM again. I can flash the kernel just fine. It's the entire ROM that seems to be the problem.
 
Kobeii said:
I updated from 0.2.1 while wiping cache and dalvik cache before flashing.
Click to expand...

Not sure if the order you do things is important, but when I flash a new update, I always clear the Dalvik Cache AFTER I flash the ROM. Maybe I've been lucky, but I have never had any issues other than multiple installs of the same app.
 
FlockaBoii said:
First GO Into TWRP
Make a backup of only your Cache
Delete That Backup
Take out your sd card and plug it into your computer
Look for a "TWRP" open it up
Go into all the folders until you cannot any more
Paste your backups
Plug it back into your phone
boot up TWRP
And Enjoy Your Restore! :)
Click to expand...
my backups are still there, I leave them?
 
Still not sure what happened to some of you that had issues with 0.2.2-r1? The only difference that I can think of that might have caused a boot loop is my wiping everything in /system/etc/init.d during the install process. I have to have some method of ensuring the proper scripts are in that directory, and I have limited tools to work with in the updater-script + updater-binary.

Did any of you that had issues with 0.2.2-r1 have any extra scripts or apps that may have made scripts in /system/etc/init.d? I know one of the users who posted troubles had something called android tweaker, and I'm pretty sure it caused the issues that user had.

Let me know of any scripts you have in init.d, and I'll see if I can figure out a better way to sweep init.d clean of scripts that might conflict with mine in the next release.
 
JerryScript said:
Still not sure what happened to some of you that had issues with 0.2.2-r1? The only difference that I can think of that might have caused a boot loop is my wiping everything in /system/etc/init.d during the install process. I have to have some method of ensuring the proper scripts are in that directory, and I have limited tools to work with in the updater-script + updater-binary.

Did any of you that had issues with 0.2.2-r1 have any extra scripts or apps that may have made scripts in /system/etc/init.d? I know one of the users who posted troubles had something called android tweaker, and I'm pretty sure it caused the issues that user had.

Let me know of any scripts you have in init.d, and I'll see if I can figure out a better way to sweep init.d clean of scripts that might conflict with mine in the next release.
Click to expand...

All I have in that is 11extsd2internalsd. I've only used CM roms, so I feel like a noob all over again. I'm really enjoying this rom though. Great job! :) I just wish I could get the latest to work. Lol
 
If anyone could pull a logcat during the bootloop, that could show what's happening (see instructions above).

Also, try pulling /data/link2sd-install-recovery.log

Paste both to pastebin.com and then post the links here.

There's definitely something different between those who are running it fine (myself included) and those of you having issues, we just have to hunt it down.

Just to be sure, no one is using a Sprint phone right, only VirginMobile?
 
Beware android tweaker is good but don't enable the fast boot or the other options which are to complicated for a normal person to understand but ensure faster performance, also make a backup, it like saving a game, literally, im suprised that a backup backed up everything the first time I did one, And its a life saver, low on memory then buy a 5 gig at least and store all your backups there and when at.bootloop put it.in and recover, I know how much.memory they are so you really want.the 5 gig.at.least so good.luck and like always have nice day
 
Hi,

I got stuck in the boot process as well . Can anyone tell me where to download
Goldmans stock rooted backup?

Also, could someone give me a quick tutorial on how to create backups?
I backed up everything using Titanium Backup before I attempted to install Victorious--but it sounds like you guys are referring to a system backup that packages into a single file?
 
monkeybiz7 said:
Hi,

I got stuck in the boot process as well . Can anyone tell me where to download
Goldmans stock rooted backup?

Also, could someone give me a quick tutorial on how to create backups?
I backed up everything using Titanium Backup before I attempted to install Victorious--but it sounds like you guys are referring to a system backup that packages into a single file?
Click to expand...

Here's g60madman's stock backup, please thank him for saving your phone! ;)
http://g60madman.vmobi.us/goghvmu/stock/TWRP.zip
And here are instructions for using it:
http://androidforums.com/5997674-post42.html

Once you have completed the instructions in that post, and have booted up, run all the updates in settings, PRL, profile, samsung software, firmware*.

Next, boot back up and restore your apps with TitaniumBackup. If you use Links2Sd, choose to redo all your links, or undo then redo them manually.

Then boot back into recovery, and select backup, be sure to check system, boot, and recovery, you use TitaniumBackup so no need to backup data, and cache will just take up space. BTW- give it a name that indicates when/why you made it, the date-stamp is borked due to the recovery not being able to access the clock properly.

Next time your phone has issues, you can restore this file you just made in recovery, and your phone will be back the way it was when you made the backup. I do a backup after each successful rom install, and/or every week to be sure I've backed up any changes I've made to settings, apps, etc.
 
mudflap2020 said:
Beware android tweaker is good but don't enable the fast boot or the other options which are to complicated for a normal person to understand but ensure faster performance, also make a backup, it like saving a game, literally, im suprised that a backup backed up everything the first time I did one, And its a life saver, low on memory then buy a 5 gig at least and store all your backups there and when at.bootloop put it.in and recover, I know how much.memory they are so you really want.the 5 gig.at.least so good.luck and like always have nice day
Click to expand...

After you make a backup you can always save them to your computer as well.:D
If you're running out of space on your phone.
 
You must log in or register to reply here.
Back
Top Bottom