[Q] Please help with bricked phone - myTouch 4G Q&A, Help & Troubleshooting

I've spent quite a while tonight FINALLY getting this MyTouch 4g (Glacier) to root and now I'm stuck in a bind.
Everything seemed to be going well and I got the Cyanogenmod 7 flashed onto the phone via Clockwork ROM Manager. Then the first time I rebooted it got to the Android logo with the spinning arrow and went into a constant loop. After about 20 minutes of this I pulled the battery and tried to restore the phone via the recovery image I created with clockwork. Here is the current status of the phone:
1. CAN get into HBOOT and HBOOT USB (but I dont think ADB can see it, or at least I haven't been able to get it to)
2. CANNOT get into recovery, phone just reboots itself to the red exclamation
3. PD15IMG.zip tries to restore the phone but fails.
What can I do to get the phone back into some sort of usable condition. I dont care where, I can start over as long as I have something to work with.

sdavidson0316 said:
I've spent quite a while tonight FINALLY getting this MyTouch 4g (Glacier) to root and now I'm stuck in a bind.
Everything seemed to be going well and I got the Cyanogenmod 7 flashed onto the phone via Clockwork ROM Manager. Then the first time I rebooted it got to the Android logo with the spinning arrow and went into a constant loop. After about 20 minutes of this I pulled the battery and tried to restore the phone via the recovery image I created with clockwork. Here is the current status of the phone:
1. CAN get into HBOOT and HBOOT USB (but I dont think ADB can see it, or at least I haven't been able to get it to)
2. CANNOT get into recovery, phone just reboots itself to the red exclamation
3. PD15IMG.zip tries to restore the phone but fails.
What can I do to get the phone back into some sort of usable condition. I dont care where, I can start over as long as I have something to work with.
Click to expand...
Click to collapse
does bootloader show Fail-PU when flashing PD15IMG.zip?

saranhai said:
does bootloader show Fail-PU when flashing PD15IMG.zip?
Click to expand...
Click to collapse
Nope, looks to me like the equivalent of what you're asking is that it says "Fail UZ"
I've attached a few screen shots for reference.
{
"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"
}

sdavidson0316 said:
Nope, looks to me like the equivalent of what you're asking is that it says "Fail UZ"
I've attached a few screen shots for reference.
Click to expand...
Click to collapse
It failed to unzip the update. Try redownloading the pd15img. This time verify the MD5SUM and try it again.

ALrighty.....this is my st00pid face. I guess in my lack of sleep last night I forgot to check the MD5SUM.
That worked....now let's see if I can break it again!!

sdavidson0316 said:
ALrighty.....this is my st00pid face. I guess in my lack of sleep last night I forgot to check the MD5SUM.
That worked....now let's see if I can break it again!!
Click to expand...
Click to collapse
Cool Glad it worked for you.

New question, essentially the same topic:
This whole thing started because I tried to flash CyanogenMod 7 onto the phone and it messed up. The phone reboots into Cyanogen and the little android on the skateboard with the arrow just goes into a repeating cycle. It will come on for 10ish seconds at a time and then just cycle back and do the same thing. I've let it go for >20 minutes and nothing changes.
Does anyone have any suggestions on how to get this ROM working? It took me so long to get it rooted with S-off that I'll be darned if I'm stopping now!
Thanks in advance!

sdavidson0316 said:
New question, essentially the same topic:
This whole thing started because I tried to flash CyanogenMod 7 onto the phone and it messed up. The phone reboots into Cyanogen and the little android on the skateboard with the arrow just goes into a repeating cycle. It will come on for 10ish seconds at a time and then just cycle back and do the same thing. I've let it go for >20 minutes and nothing changes.
Does anyone have any suggestions on how to get this ROM working? It took me so long to get it rooted with S-off that I'll be darned if I'm stopping now!
Thanks in advance!
Click to expand...
Click to collapse
Verify the MD5SUM of the ROM as well. You may of gotten a bad download.
What i personally do when i download and install a new OS is
Download OS to computer
push the OS to the SD card
verify the MD5SUM
reboot into recovery
nandroid backup
factory reset
flash new OS
flash g/apps (if needed)
reboot system
to check the MD5SUM while it's on the SDcard just use the line command from either the terminal emulator or CMD prompt.
Code:
# md5sum /mnt/sdcard/<file_name>.extension

neidlinger said:
Verify the MD5SUM of the ROM as well. You may of gotten a bad download.
What i personally do when i download and install a new OS is
Download OS to computer
push the OS to the SD card
verify the MD5SUM
reboot into recovery
nandroid backup
factory reset
flash new OS
flash g/apps (if needed)
reboot system
to check the MD5SUM while it's on the SDcard just use the line command from either the terminal emulator or CMD prompt.
Code:
# md5sum /mnt/sdcard/<file_name>.extension
Click to expand...
Click to collapse
+1
You can also check the md5 sum when its on the SDcard using the free mand5 app from the market.
Sent from my HTC Glacier Sense 3.0 using xda premium

Thanks to everyone for helping out, I finally got it working last night when I had time to sit back down with it.
I was trying to use the ROM Manager version of the Cyanogen instructions and it ended up that that was the problem. I switched over to the recovery version based on your suggestions and it worked great.
Thanks again!

General feeling around here is that the only thing ROM Manager is good for is flashing ClockworkMod recovery. There are folks who won't even do that with it.
Sent from my HTC Glacier using XDA App

ROM manager ruined my recovery I had to completely re push recovery thru adb
Sent from my PG86100 using xda premium

Related

[Guide] Foolproof way to get 2.3 without unlocking

{
"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 recently got a new Nexus One and loaded up 2.3 on it. The process is extremely simple, and doesn't require unlocking. Here's how to do it:
Download SuperOneClick to your PC. The only thing is to note is that the instructions have an extra step that should be skipped:
Turn USB Debugging OFF
Click Root
When it says: Waiting for Device, Turn USB Debugging ON
It'll now run RATC
When it says: Starting ADB Server...
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF <- Don't do this part
All BEFORE it says "Waiting for device..." again
Click to expand...
Click to collapse
From the Android Market, install Root Checker on your phone and make sure you have root access. If so, congrats, you're rooted!
Download MicroMod's Gingerbread ROM (or any ROM of your choosing) to your microSD card.
- Note: If you're not installing a new ROM and just want to use a new recovery, you need to remove two files before installing the Recovery. See this post for more info.
From the Android Market, install ROM Manager. (Thread link for more info: Amon_RA's RA Recovery)
- Select "Flash ClockworkMod Recovery" and wait for it to finish
- Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.
Click to expand...
Click to collapse
Reboot into Recovery.
- Backup/Restore -> Nand backup
- Wipe -> Wipe ALL data/factory reset
- Flash zip from sdcard -> Choose zip from sdcard -> Choose the zip of the downloaded ROM
- Reboot system now
Congrats! Enjoy Gingerbread! (And future ROM'ing!)
If you're feeling generous and you like my guides, feel free to donate.
One click doesn't work for my nexus one running 2.2.2 it gets stuck on waiting for device I turn off the phone and on while plug in to the comp and still doesn't work. am I doing something wrong?
Manual root guide...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
Why do you make people install clockworkmod first and RA then? I think CWM is just fine, it's up to the user. In any case, why not downloading RA one directly?
elegos said:
Why do you make people install clockworkmod first and RA then? I think CWM is just fine, it's up to the user. In any case, why not downloading RA one directly?
Click to expand...
Click to collapse
Because that's what the instructions say in the thread from Amon_RA himself; you know, the actual creator of the recovery. Notice it's a quote, directly from him.
Even this "Easy method" adds steps. You can skip half of your method by paying for Rom Manager and using it to flash Clockwork and a rom of your choosing.
The steps would then be to simply root (however you can), PAY for Rom Manager because it is just awesome, then install Clockwork and the latest CM7 Gingerbread nightly directly from within Rom Manager.
Clockwork and RA are very similar. I used to use RA and had no problems with it, but Rom Manager needs Clockwork to be really useful. I highly suggest paying for Rom manager and letting it do all the work.
Gaining root is the hard part. Flashing alternative roms is not. Once you root, it is smooth sailing.
Paul22000 said:
Because that's what the instructions say in the thread from Amon_RA himself; you know, the actual creator of the recovery. Notice it's a quote, directly from him.
Click to expand...
Click to collapse
Also, using flash_img in a terminal can be a little messy. CWM gives the whole process a nice GUI, even if you end up on Amon_RA.
CWM has toggles for signature and assert checks, which is a feature RA doesn't have (if it has, it's been implemented from CWM). BTW I think they're really the same thing, this is why I asked
EDIT: BTW Amon_RA created nothing but a fork of the original recovery, so he's not the creator, but a (heavy) modder
josemedina1983 said:
One click doesn't work for my nexus one running 2.2.2 it gets stuck on waiting for device I turn off the phone and on while plug in to the comp and still doesn't work. am I doing something wrong?
Click to expand...
Click to collapse
Try this: turn your phone OFF, load up SOC, then click "root" and wait till it says "waiting for device". THEN plug up your phone and power it on. That's what works for me. If that fails, download pda net on your N1 and PC and connect it. It'll install the correct/missing drivers, then use SOC as I mentioned above. That's how I rooted on 2.2.2
Sent via Tapatalk
elegos said:
CWM has toggles for signature and assert checks, which is a feature RA doesn't have (if it has, it's been implemented from CWM). BTW I think they're really the same thing, this is why I asked
EDIT: BTW Amon_RA created nothing but a fork of the original recovery, so he's not the creator, but a (heavy) modder
Click to expand...
Click to collapse
RA has signature toggles now
sitinon327 said:
Try this: turn your phone OFF, load up SOC, then click "root" and wait till it says "waiting for device". THEN plug up your phone and power it on. That's what works for me. If that fails, download pda net on your N1 and PC and connect it. It'll install the correct/missing drivers, then use SOC as I mentioned above. That's how I rooted on 2.2.2
Sent via Tapatalk
Click to expand...
Click to collapse
Thanks alot it worked like a charm.
Got my N1 from repair today with gingerbread and hboot 35. The guide isnot working for me. Please assisst
its just stuck on waiting for device. I tried doing it switched off then on but no luck. Win 7 if it makes a difference
edit: got further with installing pdanet but now on soc im stuck on
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
1209 KB/s (585731 bytes in 0.473s)
OK
chmod psneuter...
OK
Running psneuter...
Click to expand...
Click to collapse
i tried toggling usb debugging but no luck
This is driving me nuts, I was trying all night yesterday and still can't root
Only gingerbread root options are unlock the bootloader or try and downgrade and root.
Rusty! said:
Only gingerbread root options are unlock the bootloader or try and downgrade and root.
Click to expand...
Click to collapse
Then why was this thread made? And how do you downgrade?
This thread was made before Gingerbread was released...
To downgrade, you follow the "Unroot/restore" guide from the wiki, using the passimg method and the FRG33 image. It works for most people, but for some reason there's a few people it just refuses to work for...
it worked for me, thanks
Thanks it worked super for me
to use Gingerbreak babe it 's more simpler..
editing-because i rooted my nexus one
this worked like charm

[Tutorial] How To Restore Verizon Galaxy Tab Back To Stock

If you are here the odds are you are looking to take your Verzion Galaxy Tab back to the default setup for one reason or another.
Here are the steps you will need to take.
First let's make sure you have all the files and things are set up for this.
Hemdall
Download Heimdall from HERE, this is the program you are going to use to flash the needed files to your Galaxy Tab. I am putting the version I use on my sever just in case.
But here is a link to the developers page so you can download the original if you want.
http://www.glassechidna.com.au/products/heimdall/
You will also need *Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses. (I use Windows 7 and did not need to install this [I think])
Now you will need to install the drivers the is also needed for Heimdall. unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device (or whatever it says). (NOT*mass*storage)
Click start and let heimdall download/install the drivers.
Files You Are Going To Flash To Your Tab
HERE is where you *are going to download the files needed to flash to you tab.* There are four files in total.
DOWNLOAD
cache.rfs
param.lfs
system.rfs
zImage
Ok, Let's get to flashing over the files and getting your tab back to normal.
1: Connect your tab to your PC
2: Launch your tab into download as it is already connected to your PC.*(Do this by holding the volume down and pushing the power button)
3: Go in to the folder " heimdall" and start " heimdall-frontend.exe"
4: Set up the files you are about to flash to the tab in side of heimdall.* It should look something like this.
THIS IS THE IMPORTANT PART!!!!!! DO NOT SCREW THIS UP - -* I AM NOT RESPONSIBLE!!
DO NOT EVER EVER EVER PUT ANYTHING IN ANY OTHER LOCATION. THESE ARE THE ONLY FILES YOU NEED.
zImage goes in both the Kernel AND Recovery slot.
system.rfs goes in Factoryfs
Param.lfs goes in Param.lfs
cache goes in the cache slot.
{
"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"
}
5: After you have the files in place click start to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems. (I had to push start a few times.)
After this runs you will more than likely boot loop. Power down, wait a few seconds and hold power and up volume to boot into recovery.*(NOTE, do not hold power too long, just long enough to turn it on, then continue holding up volume till you see recovery. WIPE DATA AND CACHE. Tab should boot.
Note, if heimdall fails at the very beginning, just try unplugging and turning off the tab, close, and relaunch heimdall. it will eventually start. sometimes you just need the right combo of plugging in launching the*program.
After this is should be just like you took it out of the box, other than still having root access.
Hope this helps!
Aslo, I did not do any of the work here other than test it out and retype what is on this site to make it available to those on XDA and if you read my blog.
http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11.html
All credit should go to mike919 at droidforums.net for putting this together!!
You can view his post here.
http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11.html
Shameless Plug:
If this helped you out would you do me a favor and go to this site and vote/comment?
And pass it along to your friends as well.
Who Pees In The Shower?
Hope this helps some people out around here!
This should be a sticky... Just Saying
Thanks,
I tried to make sure I typed it as good as I could so people like me (mess things up often) would be able to pull it off and host all files I use so that nothing will change.
But I would like someone to look it over and make sure I did not miss something. We are all human after all.
And if there needs to be any other images people can think of to help more people out I will be more than happy to add them.
I cannot find ANY tuts like this for flashing roms, recovery, ect. You, my newfound friend, are the first. We need more exactly like this.
Sent from my SCH-I800 using XDA App
This is great stuff. I messed up a bunch of junk on my VZ galaxy tab and would like to go back to stock. Question about this guide: I've converted to ext4. Can I still follow the steps in this tutorial to return to stock or is there anything else that I need to do first? Thanks very much!
This post made even a retard like me dangerous enough to want to try flashing. Bump for the ext4 answer
Bobby Buggs said:
This post made even a retard like me dangerous enough to want to try flashing. Bump for the ext4 answer
Click to expand...
Click to collapse
Took the plunge anyway. Seems to have worked. Great tutorial!
Had previously used Koush's bootstrapper from the market to convert the file systems to ext4. Later tried to install KhasMek Voodoo Plus v3 kernel on my VZW tab and it nuked it (prob cause I did something wrong). Using these instructions, I got back to stock. Now to boot strap again and try, try again!
Thanks for the guide
fonixmunkee said:
Had previously used Koush's bootstrapper from the market to convert the file systems to ext4. Later tried to install KhasMek Voodoo Plus v3 kernel on my VZW tab and it nuked it (prob cause I did something wrong). Using these instructions, I got back to stock. Now to boot strap again and try, try again!
Thanks for the guide
Click to expand...
Click to collapse
Yeah, I think I get it wrong more than I get it right.
Last weekend I did this like 3 times in an hour.
Happy it is helping a few people out.
chaos67731, I saw in another thread you were having a hard time getting Koush's boot strapper from the market to work. Did you ever get a resolution for that?
fonixmunkee said:
chaos67731, I saw in another thread you were having a hard time getting Koush's boot strapper from the market to work. Did you ever get a resolution for that?
Click to expand...
Click to collapse
No, I tried a few times and did not have any luck. The only thing I am looking to customize with the Tab is really to have it over clocked a little.
I just got the Evo so after I am done setting that up and getting everything worked out I am going to try again.
But if I remember right when ever I run Koush's boot strapper the tab reboots and goes in to recover mode and starts to flash something. (I think, cant seem to remember 100% right now) . Then I get stuck on the Samsung screen..
At that point I am not able to boot back in to recovery mode to wipe anything, but I can boot in to download mode and restore the Tab.
I think I have to be missing something simple?
Got the bootstrapper from the market to work again on my VZW Galaxy Tab. Formatted the SD card and then tried it again...it worked great after that!
Sent from my SCH-I800 using XDA Premium App
fonixmunkee said:
Got the bootstrapper from the market to work again on my VZW Galaxy Tab. Formatted the SD card and then tried it again...it worked great after that!
Sent from my SCH-I800 using XDA Premium App
Click to expand...
Click to collapse
Maybe I am missing something?
Sent from my SCH-I800 using XDA Premium App
hi after restore to stock my screen in blank??help me
this was perfect
you wrote the directions clearer than water bro. thanks! i was dinking around for the 1st time with the tab and screwed something up. i'm back in business!
Your the best... got it first time Great work
- The Mike G.
Had a scary night last night with the old computer/phone/exclamation point error screen but this tutorial helped me out. Thanks a ton.
THANK YOU!
Thanks man! My Galaxy Tab (us cellular branded) was gone after a flash attempt gone bad (black screen and nothing more), but thanks to this tutorial it's finally back to life!!
I LOVE YOU MAN!
VZW Custom Kernel
So out of curiosity, is the Bootstrapper the only way to get a custom recovery set up for the Verizon tab? I used z4root and got the root access, but since then, I haven't had an opportunity to flash roms or kernels because of the lack of a custom recovery. Anybody think they could help ?

Stock ROM constant reboot on white HTC EVO 4G screen

Hi all,
Here's short history of the phone:
Friend of mine drop his on the concrete about June of last year and whole screen was cracked (not pretty). About month ago I found LCD Screen with Digitizer on ebay bought it and replaced it.
After turning it on everything was working except random reboots. Phone was not registered to any account so there was no internet only WI-FI.
So I started going into system updates and downloading HTC updates it did two of them and I think on the 3rd one it just starts to boot white HTC EVO 4G screen comes on and then it reboots.
Only pulling the battery will stop it.
This is all on stock HTC Sense ROM, rooting was never attempted!
I've searched thru the forums here but everything here relates to failed rooting process.
Can someone please make any suggestions?
Bellow is the pictures of boot loader.
Help is greatly appreciated!
{
"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"
}
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Fazulka said:
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Click to expand...
Click to collapse
Thank you!
Followed the instruction, run RUU and it starts to check the phone after this I get error[170]: USB connection error.
I've tried over 10 times.
Step 4 says "Make sure USB debugging is enabled on your phone."
I can't even log into Sense?
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
ffolkes said:
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
Click to expand...
Click to collapse
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
JohnnyBeGood113 said:
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
Click to expand...
Click to collapse
I had to unroot mine and I found that u have to have the right pc36img file. If you dont know what ver rom was running then you may need to try them all. But I had the same problem it just wouldent install the file. Keep trying and if you need help finding them Ill help ya.
I found this but its not the same place I got mine from. http://www.filecrop.com/htc-evo-4g-roms.html
Thanks for the reply!
Somewhat of a progress. I tried countless times and it always gives me USB connection error: Then I downloaded HTC Sync and and I think I went to Hboot and I heard sound on windows it seemed like phone got recognized and I was able to finish the processes. It was flashed using RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed. Then when I went to again in recovery it was again red triangle over the phone.
After that I just let it try to boot and it finally booted into HTC sense!
Turned on WI-FI and wanted to check if there's any updates and it said no updates?
This is what recoveries I've tried so far:
Amon RA 2.1.1
Amon RA 2.2.1
Amon RA 2.3 (Added 02/09/2011)
Stock Recovery 3.26.651.6 (Added 01/18/2011)
Stock Recovery 3.29.651.5 (Added 01/18/2011)
Stock Recovery 3.30.651.3 (Added 01/18/2011)
Stock Recovery 3.70.651.1 (Added 01/18/2011)
One by one I tried each one renaming to PC36IMG.zip and none of them asked me if I want to do the update. It just checks it and goes back to bootloader.
Why do I get red triangle?
What should I do now?
Help is appreciated!

My Glacier is semi-bricked...?

Okay, so I was on the Stock 2.3.4 GB rooted rom, I tried to flash Android Revolution but somehow I downloaded the Sensation one and tried to flash and it gave error Status 7 (4EXT).. So, I went back to stock 2.2.1 and perm-rooted and my S if still off, so I flashed recovery and tried to flash Runny Mede, it dosen't dare to pass the MyTouch 4G logo, and just starts a boot loop right there. Please help, I want to enjoy other roms just like you guys too! Also, everytime I mount my phone as a Disk Drive, windows asks me to Scan for errors, I do it (with both options checked) and it just immediately closes and goes into the root of my SD.. Please help me.
Make sure when flashing a new rom to wipe data/cache. I'd recommend wiping system too, just to make sure you don't run into other issues.
This comes from memory only, (Anyone- don't hesitate to correct me if I'm wrong) and I couldn't find any info about it to confirm, but I believe Status 7 simply means the installation of the zip file you attempted to flash was aborted, i.e. nothing was flashed. Many ROMs have checks in them to confirm you're flashing to the correct device, and if not, will refuse to proceed, and this may be what you encountered.
As for Windows asking you to scan for errors, this happens any time you disconnect your phone or unmount it without safely ejecting via Windows. It's unlikely you would actually have any disk problems or corruption unless you disconnected or unmounted while files were still being transferred or edited. Safely unmounting would be considered the best practice. When you're ready to disconnect your phone from your computer, or to unmount the SD card from Windows, look for an icon 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"
}
Click it and choose your device to safely remove it from your computer.
Going back to froyo and "re-rootong" was a complete waste of time.
Status 7 would indeed mean nothing was flashed (nice post by the way, to the guy above me).
All you needed to do was wipe system, data and cache a flash the correct ROM. Alternatively, you could have restored the backup that you should have made before you tried flashing ARHD.
Try holding Vol down at boot to get to bootloader. Once there select Recovery. That will get you on the right path. Remove PD15IMG from the root of your SD before you do this.
Edit: I just remembered that your recovery is stock if you flashed PD15IMG. You will need to flash a recovery.img with adb. The steps are in the clockworkmod thread that is stickied in the dev section. There used to be a PD15IMG of an older 4EXT recovery floating around. You might try locating that.
crawler9 said:
Make sure when flashing a new rom to wipe data/cache. I'd recommend wiping system too, just to make sure you don't run into other issues.
This comes from memory only, (Anyone- don't hesitate to correct me if I'm wrong) and I couldn't find any info about it to confirm, but I believe Status 7 simply means the installation of the zip file you attempted to flash was aborted, i.e. nothing was flashed. Many ROMs have checks in them to confirm you're flashing to the correct device, and if not, will refuse to proceed, and this may be what you encountered.
As for Windows asking you to scan for errors, this happens any time you disconnect your phone or unmount it without safely ejecting via Windows. It's unlikely you would actually have any disk problems or corruption unless you disconnected or unmounted while files were still being transferred or edited. Safely unmounting would be considered the best practice. When you're ready to disconnect your phone from your computer, or to unmount the SD card from Windows, look for an icon like this.
Click it and choose your device to safely remove it from your computer.
Click to expand...
Click to collapse
estallings15 said:
Going back to froyo and "re-rootong" was a complete waste of time.
Status 7 would indeed mean nothing was flashed (nice post by the way, to the guy above me).
All you needed to do was wipe system, data and cache a flash the correct ROM. Alternatively, you could have restored the backup that you should have made before you tried flashing ARHD.
Try holding Vol down at boot to get to bootloader. Once there select Recovery. That will get you on the right path. Remove PD15IMG from the root of your SD before you do this.
Edit: I just remembered that your recovery is stock if you flashed PD15IMG. You will need to flash a recovery.img with adb. The steps are in the clockworkmod thread that is stickied in the dev section. There used to be a PD15IMG of an older 4EXT recovery floating around. You might try locating that.
Click to expand...
Click to collapse
Thanks to both of you, I tried flashing TRAD v1 and it worked, made a nandroid, just flashed virtuous Affinity maybe 2 minutes ago and its booting. I guess I just panicked a bit. c:
It's easy to do if you aren't used to flashing. Those minor heart attacks aren't fun, either.
Tell me about it. : )

VS980 TWRP bootloop after botched lollipop OTA while rooted like a dummy

So yeah. As the title says I had a rooted VS980 on 4.4.2 with some bloat removed and I accidently hit the wrong button when prompted for the upgrade, I was in a hurry. yes, I'm a moron, and yes, I know this is probably wasting someone's valuable time and I thoroughly apologize for my n00bishness
having said that, I have tried to go through various tuts but none of them seem to be working. yes, it's likely that I am simply doing it wrong, but whatever the case I am stuck with my phone in a bootloop always returning to the TWRP recovery. I believe that means it is soft bricked so I'm hoping this can be fixed fairly easily with the right direction and some patience for my ignorance. I can't seem to get it into download mode with turning it off, holding the volume+ button and plugging it in, it just goes to twrp. :'(
my hope is to get a rooted lollipop. if that is not possible then I would be fine with going back to stock or possibly even a custom rom if it's not too awfully complicated. honestly, I'm at a point where I'm beginning to accept that I probably shouldn't be screwing around with it too much and will likely bite the bullet and just keep my phone stock since there are really only a few minor irritants that make me want to root it.
any help is very much appreciated.
anybody? pretty please? any ideas at all?
Deviouz1 said:
anybody? pretty please? any ideas at all?
Click to expand...
Click to collapse
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
a.perkins89 said:
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
Click to expand...
Click to collapse
actually, it doesn't look to be the same problem. i dont have download mode, but i do have recovery. it boots to twrp like a champ. what i think i really need is how to get the flash file VS98011A_01.zip on my phone via ADB Sideload, specifically when i cant get the drivers to work.
i've tried the following drivers:
LG_VZW_United_WHQL_v2.14.1.exe
LG_VZW_United_WHQL_v2.20.0.exe
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1_3.10.1.0
I may very well be mistaken about what needs to happen, i'm no expert, obviously, but from everything ive read any of those should have worked. i think if i can get the right flash on the phone i should be able to flash it via twrp no?
I"ll help
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Jaqueezzzy said:
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
awesome,thanks you, i'll try that!
Deviouz1 said:
awesome,thanks you, i'll try that!
Click to expand...
Click to collapse
Just so you know it talks about flashing a ROM, but just use the zip you need insted, because it's the same principal.
Step 9 Fails.
{
"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 just happened to have a brand new data cable, tried again with same result so its not media related unless there is an issue with the plug itself, but it's charging and the Device manager shows the correct name ie VS980, it just has a yellow bang on it and i cant find a driver that changes that.
read some more and found others with the same issue apparently which led me to here: http://forum.xda-developers.com/showthread.php?t=2715408
which is where i found the "download mode restore" file you mentioned(i didnt see it in the thread you provided), but without the ability to get adb usb command to work i dont see how i can use it.
any ideas?
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
siggey said:
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
awesome, ty sir. i happened to have one of those laying around from when i cracked my screen on my old one and couldnt interact with the screen. took a while to find it buried but i have it and i have successfully been able to access a thumb drive. i think that might be all i need.
will report back though regardless.
ok, now i'm rrrrrEEAALLYY freakin confused...
successfully flashed (via the install section of twrp with usb otg thumbdrive mounted.)
xdabbeb_vs98028a_bootstack.zip
and
xdabbeb_vs982.5_1.1.0.zip
from
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
but when i reboot, it goes directly to twrp still.
wat? :'(
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
WOO-FREAKIN-HOOOO!!!
at the setup wizard now.
Deviouz1 said:
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
Click to expand...
Click to collapse
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
thecadman99 said:
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
Click to expand...
Click to collapse
sweet, i'm glad someone else found it useful.
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
thecadman99 said:
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
Click to expand...
Click to collapse
Is your baseband recognized by chance?
Deviouz1 said:
Is your baseband recognized by chance?
Click to expand...
Click to collapse
Nope... its UNKNOWN
And I have not download mode
And I have not cdc serial showing up when connected
And TWRP and Root are gone
I'm starting a new thread for help- I've been working on this for 2 days lol.
Thanks for the reply!

Categories

Resources