FUBAR After AOSP 1.6 - PLEASE HELP - Hero CDMA Q&A, Help & Troubleshooting

So I was trying to troubleshoot an SMS issue with AOSP 1.6 so I decided to flash back to Fresh 1.0. I also performed a wipe/factory reset. Fresh would not boot - it would just endlessly loop through the boot process, crashing at various points. I tried Fresh 1.1. Same problem. I re-downloaded Fresh 1.0 to make sure my file was not corrupt, flashed that, and have the same problem.
So I decided to start trying to recover from my various backups. What do you know - every single one is corrupt. From adb I see:
Code:
Verifying backup images...
boot.img: OK
cache.img: OK
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: FAILED
md5sum: WARNING: 2 of 6 computed checksums did NOT match
On every single one. Even if I make a backup and immediately try to restore it I see this error. I also tried backups of my backups and each of those failed as well. Any way to force these to restore?
So I checked my SD card with various tools - no problems found.
So now I'm left unable to flash 1.5 or restore from or make any backups.
Does anyone have any ideas what could be wrong or what I should do to fix it? What other information could I provide?

honestly I would try to RUU and reroot and then try flashing a backup it may not be that the backups are corupt put that something isnt letting it read that part of the backup correctly.

gthing said:
So I was trying to troubleshoot an SMS issue with AOSP 1.6 so I decided to flash back to Fresh 1.0. I also performed a wipe/factory reset. Fresh would not boot - it would just endlessly loop through the boot process, crashing at various points. I tried Fresh 1.1. Same problem. I re-downloaded Fresh 1.0 to make sure my file was not corrupt, flashed that, and have the same problem.
So I decided to start trying to recover from my various backups. What do you know - every single one is corrupt. From adb I see:
Code:
Verifying backup images...
boot.img: OK
cache.img: OK
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: FAILED
md5sum: WARNING: 2 of 6 computed checksums did NOT match
On every single one. Even if I make a backup and immediately try to restore it I see this error. I also tried backups of my backups and each of those failed as well. Any way to force these to restore?
So I checked my SD card with various tools - no problems found.
So now I'm left unable to flash 1.5 or restore from or make any backups.
Does anyone have any ideas what could be wrong or what I should do to fix it? What other information could I provide?
Click to expand...
Click to collapse
Have you tried to use the RUU to return to complete sock and then just re-root? The RUU does not depend on your SD card, just in case that is the culprit. There is a link on my sig. If not that would be my next step.

wtphoto said:
honestly I would try to RUU and reroot and then try flashing a backup it may not be that the backups are corupt put that something isnt letting it read that part of the backup correctly.
Click to expand...
Click to collapse
Beat me to it.
But a quick thread hijack real quick. I see in your sig you have a horizontal fresh nexus hybrid bootscreen. care to share the source. Sounds cool.
Back on track after this I promise

rockcrawler said:
Beat me to it.
But a quick thread hijack real quick. I see in your sig you have a horizontal fresh nexus hybrid bootscreen. care to share the source. Sounds cool.
Back on track after this I promise
Click to expand...
Click to collapse
give me a min and I will post a flashable zip in the theme sticky
now back to the helping.

Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?

gthing said:
Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?
Click to expand...
Click to collapse
Yes. Boot into whatever ROM you can and then try again.
I assume that you have had the ADB drivers working before?

gthing said:
Trying to flash RUU from the Fresh blog now. For some reason it is failing to see my phone when it is trying to flash. Could it be because I am in recovery mode?
Click to expand...
Click to collapse
no this has been brought up a few times you need to make sure you have the most recent sdk installed then copy and paste the adb.exe, adbwinapi.dll and the fastboot.exe into the ruu file then try again.

wtphoto said:
no this has been brought up a few times you need to make sure you have the most recent sdk installed then copy and paste the adb.exe, adbwinapi.dll and the fastboot.exe into the ruu file then try again.
Click to expand...
Click to collapse
+1 on this,
Someone should update the ruu thread to include this.

Installed the adb driver (no, I didn't have it previously) and copied the files from the latest SDK. No luck still but I'm going to keep trying.

you could also try booting into fastboot and trying it who knows it might be becuase you are in recovery just poer off and hold volume down and power at the same time to get into fastboot and try it that way.

wtphoto said:
you could also try booting into fastboot and trying it who knows it might be becuase you are in recovery just poer off and hold volume down and power at the same time to get into fastboot and try it that way.
Click to expand...
Click to collapse
That did it! Flashing now! Thanks!
EDIT: Maybe I spoke too soon. The flasher is stuck at "erasing user data..." and is showing 0% and the phone is showing the htc boot screen. I don't know if it's safe to cut it off and start over or not.
Windows had to increase virtual memory in the middle of the operation and I think it jacked things up ....

np glad to help.

Yea ... it seems to be getting stuck on "Erasing user data...." not sure what to try next.

unfortunatly thats the extent of the knowledge that I have I would try contacting gbhil or toast or fresh or one of the other devs to see what they say.

Pull battery, do a factory reset (BACK+HOME+POWER) & then attempt to reflash RUU.

gu1dry said:
Pull battery, do a factory reset (BACK+HOME+POWER) & then attempt to reflash RUU.
Click to expand...
Click to collapse
No luck... I give up for tonight...

gthing said:
No luck... I give up for tonight...
Click to expand...
Click to collapse
That really sucks.

same thing
The same thing happened to me when i tried to flash gumbo 1.5c. I flashed RUU and then re-rooted that resolved my issue..

Turns out my problem was that I was trying to flash the RUU from a virtual machine. I'm used to being able to flash WM roms from a Windows VM but apparently it doesn't work with the Android tools. I could also not use the auto-rooter from the VM.
I had to track down a Windows machine () and then was able to get everything flashed and running without too much trouble.
Thanks for everyone's help on this. My phone is now back up and running and I was able to confirm the problem I was having: AOSP 1.6 radio is incompatible with the airave and will cause you to not be able to send SMS messages.

Related

[Q] Restore samsung default recovery

I rooted and installed clockwordmod recovery using the information on this forum, now I want to revert to stock recovery. I followed the instructions on this page
showthread.php?t=731989
Click to expand...
Click to collapse
and did a master clear and the regular flashing process. Everything seems to be working fine except when I reboot into recovery mode and select reinstall all packages i get this error:
e: can't open /sdcard/update.zip.
Click to expand...
Click to collapse
I tried two different Odin packages I897UCJF6 and I897UCJF1, both give me the same issue.
I think my only option is to use a nandroid backup from a fresh install, can anyone send me a link to one please.
If you did a master clear it deleted everything on your /sdcard volume... so of course it isn't finding an update.zip package there =P
if your recovery is black screen w blue letters, That is samsung recovery.
Zilch25 said:
If you did a master clear it deleted everything on your /sdcard volume... so of course it isn't finding an update.zip package there =P
Click to expand...
Click to collapse
I dont think theres supposed to be an update.zip on the factory device, besides odin is supposed to be a complete image
Sent from my SAMSUNG-SGH-I897 using XDA App
iamamp3pimp said:
if your recovery is black screen w blue letters, That is samsung recovery.
Click to expand...
Click to collapse
I can get to samsung recovery, but when I click reinstall packages it fails if there isn't an update.zip file in the /sdcard directory.
I poked around the clockworkmod update.zip and found out it deletes the /cache/recovery/update.zip and installs a modified /sbin/recovery; among other things, but I think those are the files that are most important to me right now, are those files not restored by Odin?
btw I'm new to android but I'm a linux admin and programmer so I have a basic understanding of how this works, now to just dig deeper and find out where it's going wrong.
Odin will wipe everything on your NAND clean, this does not include the /sdcard area (internal Sdcard)
Doing a master clear wipes everything including your internal sd (so if you had already had a clockwork backup it would have gotten wiped as well)
Rom Manager/Clockwork creates a folder on your /sdcard called /sdcard/clockwork, and within that folder all of your images are stored. Clockwork uses and update.zip file to install itself on boot up (through stock recovery)
I'm not entirely sure what answer you're looking for though, so I figured I'd just lay out a few facts in hopes that one of them might help
Thanks for the reply, I know the basics of how clockworkmod/nand work. What I'm trying to do is restore my phone to factory condition, Odin restores everything except the recovery manager, for some reason I'm stuck with the modified recovery that needs an update.zip. Before I made any changes, when my phone was new, if I booted into recovery and selected reinstall packages it would run the default att/samsung recovery program and reinstall default packages(as far as I can remember, please tell me if I'm just imagining this, ive been flashing and reflashing my phone countless times so I could be really confused), thats what I wan't to happen, now it just gives me the error:
e: can't open /sdcard/update.zip.
Click to expand...
Click to collapse
I don't recall my stock phone doing that, otherwise I wouldn't of had to return my first phone , black screened it on the first day I had it lol.
tbae2 said:
I don't recall my stock phone doing that, otherwise I wouldn't of had to return my first phone , black screened it on the first day I had it lol.
Click to expand...
Click to collapse
lol thanks, do you mean that it didn't try to reinstall the packages?
And could someone else with a stock AT&T Captivate please confirm, I'm not ready to admit that I've gone completely crazy....
Just so I understand. You go to recovery and it tries to install an update.zip without you doing anything? This isn't normal.
I'd do another odin and a master clear. That really should do it.
gunnyman said:
Just so I understand. You go to recovery and it tries to install an update.zip without you doing anything? This isn't normal.
I'd do another odin and a master clear. That really should do it.
Click to expand...
Click to collapse
No, he is saying that when he first got the phone it used to reinstall the stock packages when he selected reinstall packages. Now it doesn't and instead just says it can't find update.zip. He just wants to make sure that on a stock recovery it's not supposed to install anything when he selects reinstall packages.
If you did a master clear and have not manually put an update.zip file back into the root of the sdcard, then you will always get that message because the file does not exist. If you ran the 1 click odin and restored the phone, then you are back to stock. No further actions necessary.
Sent from my SAMSUNG-SGH-I897 using XDA App
gunnyman said:
Just so I understand. You go to recovery and it tries to install an update.zip without you doing anything? This isn't normal.
I'd do another odin and a master clear. That really should do it.
Click to expand...
Click to collapse
I've done a few master clears using odin. It's not trying to install an update.zip without me doing anything, the way I remember it on the stock phone when you select reinstall packages it will reinstall the default att packages, am I wrong about this?
kaiserman023 said:
I've done a few master clears using odin. It's not trying to install an update.zip without me doing anything, the way I remember it on the stock phone when you select reinstall packages it will reinstall the default att packages, am I wrong about this?
Click to expand...
Click to collapse
You are wrong about this. Selecting reinstall packages tells the phone to look for an update.zip file.
alphadog00 said:
You are wrong about this. Selecting reinstall packages tells the phone to look for an update.zip file.
Click to expand...
Click to collapse
Solved. Thankyou
Turns out there was nothing wrong with the phone just me, I've been trying to fix something that isn't broken!!!
alphadog00 said:
You are wrong about this. Selecting reinstall packages tells the phone to look for an update.zip file.
Click to expand...
Click to collapse
this......
Lol Jeez with all the hard issues we get around here it's the simple questions that confuse the crap out of us
Thread moved to Q&A.

[DEV] ClockworkMod 5.5.0.4 [UPDATED: Can't get to CWM? Here's the fix!]

Howdy y'all!
I just compiled a proper version of ClockworkMod recovery 5.5.0.4 off of the ICS branch of CyanogenMod.
It supports backing up boot images (I have heard that the image that is being flashed now doesn't support backing that up), and in the near future will support recovery chargemode.
This repository will hopefully contain in the near future a semi-working copy of CyanogenMod 9 also, but there's no guarantees on that one
So, without further ado:
What is this?
This is ClockworkMod Recovery 5.5.0.4 and the files necessary to build it yourself.
Click to expand...
Click to collapse
How do I use it?
You must first be unlocked with HTCDev.com (there is an excellent guide over there, just click on the Unlock Bootloader button and it'll walk you through)
Once you're unlocked, download the prebuilt image below, and do the following (in the same directory you used to unlock your phone):
Code:
fastboot flash recovery <path/to/prebuilt-image-you-downloaded.img>
You need to replace the stuff in brackets with the path to the img file you downloaded from here...
Alternate Installation Method (ph39img)
Much easier installation once unlocked with HTCDev...
Simply download the ph39img.zip I have linked to in the downloads section, and put it on your external SD card.
Reboot your phone into HBOOT, and allow the update. Then you've got clockwork installed super easy, no computer needed!
Click to expand...
Click to collapse
How is this different from the ClockworkMod image that's floating around here?
Truth be told, I haven't tried the other version yet-- but I have been told that it doesn't back up boot.img, and has a few other bugs.
Also, this version has /sdcard mapped to the external SD card as opposed to the internal SD card. This is a safety feature to prevent losing backups in case your device becomes inaccessible. All backups should be to an external storage medium (even on your desktop, it's a good practice to not backup your hdd to the same device )
I'm sure mine has bugs too, but I'm posting the source so y'all can laugh at me
Click to expand...
Click to collapse
The Goods: Where do I get it? -- Downloads:
recovery-beta2.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-beta2.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG-chargemode.zip
New! PH39IMG.zip for users with ICS OTA: http://goo-inside.me/private/iomonster/htcvivid/recovery/ph39img/hboot-1.85/PH39IMG.zip
Click to expand...
Click to collapse
recovery-take1.img - https://github.com/downloads/thecubed/android_device_htc_holiday/recovery-take1.img
Alternate installation method: ph39img.zip : https://github.com/downloads/thecubed/android_device_htc_holiday/PH39IMG.zip
Click to expand...
Click to collapse
The GitHub source is here:
https://github.com/thecubed/android_device_htc_holiday
Click to expand...
Click to collapse
Please don't mirror the files (hotlinking is okay!), just incase I need to take them down or quickly update them. Thanks!
Click to expand...
Click to collapse
Changelog
recovery-take1 : initial release
recovery-beta2 : now supporting charge mode in all forms just like stock recovery, and a few behind-the-scenes tweaks
Click to expand...
Click to collapse
Tips and Tricks (what works, and what doesn't)
Please read the following-- the HTCDev unlock comes with it's own disadvantages and risks...
The HTCDev unlock adds the word "**UNLOCKED**" to your HBOOT screen. Even if you put your phone to stock with a RUU and re-lock the phone, your phone will show "**RELOCKED**" when booted to the bootloader.
At this time, I am unsure if AT&T will refuse warranty claims if they see that text. Just remember: if you unlock, there may not be any way back to complete stock any time soon.
Another disadvantage of the HTCDev unlock: ClockworkMod recovery CANNOT flash kernels. You must use JoeyKrim's kernel flasher ( http://forum.xda-developers.com/showthread.php?p=20926830 )or fastboot to flash kernels. This includes Nandroid backups.
If you back up your phone and apply a new ROM and kernel, you will have to fastboot flash the old boot.img back or use JoeyKrim's kernel flasher before switching ROMs.
If you flash a ROM, make sure to read the instructions with the ROM. Every ROM developer has a different method of flashing the kernel-- some come with a script to run, and others just give you the files to flash. Please read what they have to say before posting here with a complaint
Not seeing your rom .zips on your SD card, or having trouble restoring a backup?
This version of ClockworkMod has the external SD card set as primary. This is to avoid the problem of "my phone died, and I can't access my backups".
To solve this issue, simply put your ROMs or whatnot on your external SD card. In the future, I may look into how hard it is to add a internal/external SD switcher to clockwork, but for now the safest default is the external SD.
Sorry about that!
Some rom.zip's don't work...
This may be because they're using an old version of the update-binary in their .zip file. Contact your ROM maintainer and ask for an updated version
If you are a ROM developer, here's the updated "update-binary". Drop it in your META-INF/com/google/android directory in your ZIP and update your format() commands properly...
update-binary.bin (rename to update-binary) - http://legacyschool.us.to/htcvivid/update-binary.bin
Click to expand...
Click to collapse
HELP! I CANT GET INTO RECOVERY! *new!
If you find yourself unable to get into CWM (i.e. the screen flashes some text, then reboots immediately), just boot to fastboot (hboot -> fastboot), then issue "fastboot erase cache" on your PC.
Then you should be able to boot into ClockworkMod. After you're in there, make sure to format /cache to fix the problem.
This issue will be fixed soon, I'll add some intelligence to the kernel to not bother rebooting to fsck a partition if it's marked 'dirty' or unmountable. Stock recovery is supposed to fsck the partitions if they're dirty/broken, but CWM doesn't bother, and the kernel gets easily confused.
Click to expand...
Click to collapse
How can I contact (chastise, praise, call names) you?
On IRC (Freenode) you'll find me hanging out in #htc-holiday when I'm available.
Just say my name "IOMonster" (or "IOMonster_desk") and if I'm around I'll answer.
I also will sometimes respond to PM's on XDA, but XDA's forum has a bad habbit of not emailing me when I get a new PM...
Click to expand...
Click to collapse
Standard "it might not work" clause
This software hasn't been thoroughly tested, and it might not work.
It might not backup things correctly, and it might not restore them right.
Please don't trust this software with anything sensitive or life-alteringly important.
I'd hate to say "I told you so!"
That's not to say this software doesn't work, it's just the standard disclaimer.
Click to expand...
Click to collapse
Donation Information
I love to develop. I don't do this for money, I do it just for the "thanks".
Please don't feel obligated to donate, but if you feel like it, you can click the button below to donate a small amount to me. Alternatively, consider donating to a charity of your choice-- there are so many good causes out there that could use your donation.
​Thank you in advance!
Click to expand...
Click to collapse
Credits / Thank You's
IanWizard-cloud (testing, moral support )
Pirateghost (much needed debugging, testing, and flashing his phone no less than 20 times!)
joeykrim
toastcfh
fattire
BananaCakes (for getting clockwork built in the first place and enabling so many mods on day 1 of unlock!)
..and lots of others!
Click to expand...
Click to collapse
Thanks for giving this looong post a read!
Good luck!
Shoot I'll give it a shot. Flashing now. Will edit this post after its been tested.
Edit: Short glance review, I know a lot of this is already stated/known but just posting it anyways
So firstly, I'm still getting no confirmation when I flash images (whether it be recovery or kernal) but again, I think thats from me using a VM to do all the work.
Still boots into recovery when plugged in.
Maybe I'm just being an idoit, but I couldn't get out of the keytest, had to hold power button which booted the rom.
Of course the usb mount and such works.
Will try backup later when I'm not short on downtime.
already flashed... beautiful. will run through some tests tonight. and dont think you are getting rid of me on IRC now
Coming from the HTC EVO 3D land with the HTC unlock method for the last 6 months .. the following tips have been very helpful.
HTC Unlock method only allows kernel write access while in two modes, fastboot and standard android mode. HTC unlock method does NOT allow a kernel to be flashed from standard recovery mode. This includes a ROM .zip with a kernel inside. The ROM will load, but the kernel will not from standard recovery mode.
The ONLY way to flash a kernel whether by performing a full nandroid restore including the kernel or flashing a ROM with a kernel inside, is to use the following command to load the custom recovery:
fastboot boot <destination of recovery.img>
example on windows: fastboot boot c:\downloads\cwm-recovery.img
Everything else will work in the standard custom recovery mode EXCEPT the ability to flash a kernel. To flash a kernel through the custom recovery, fastboot mode must be used per HTC's unlock method.
Updated OP with simpler installation method (ph39img).
Much easier to use, and no mucking around in commandline!
well it most definetly worked. i jus downloaded the zip file and was able to back up my settings. Only problem i have is. ( which is a similiar problem i had before this. if i powered off the phone and plug it to charge it would automatically restart the phone.) When i power off now and plug it in to charge. It automatically goes to the clockworkmod set up. none the less my phone works and i have backed it up. But i still was wondering wat could cause these problems ?
Same issue here can't charge while off,
I not sure boot backups are working,
Was stock did back up, flashed RR betas and then restore to saved image, got bootloop, had flash boot thru fastboot
Sent from my HTC PH39100 using xda premium
Great start for this....from what i was told theres drivers needed in the recovery for it to charge while device is off and fastboot is unchecked...device charges while fastboot is checked and device is off....
WC
Recovery works great for me.
BTW, the offline charge issue is usually in the chargemon file.
for the new recovery, we will need to be using a new update-binary and when flashing a rom, your updater-script must contain 4 arguments in the format line, like this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
inside the attached zip you will find the update-binary
if you dont know what update-binary and updater-script is, then this isnt for you and you needn't concern yourself with it.
Just put your new recovery in the superguide and gave you credit. Keep up the good work!
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
drewdatrip said:
There seems to be some issues pertaining to this CWM and flashing Telstra_boot image and attempting to install Run Runner ROM.
After flashing boot.img and attempting to wipe and isntall the rom i got an aborted error 1. After rebooting back into recov i was stuck at the HTC boot screen
The only way i could get back and working was relocking and flashing the RUU
Drew
Click to expand...
Click to collapse
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Pirateghost said:
Did you not download the fix I provided in the Rom thread? This recovery works fine with the updated binary.
Sent from my HTC PH39100
Click to expand...
Click to collapse
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
drewdatrip said:
I did notice your fix but i was already about half way through the "long way"
Needless to see im using the slightly older version of CWM and now on RR10
Drew
Click to expand...
Click to collapse
At that point it was too late for.the fix. It does work now though.
Sent from my HTC PH39100
Question has the flash able zip been updated so it will now work to flash rooms or is it the rom zip scripts that needed updating? Can I place this zip on my SD card and overwrite the old version ( if that's what was in fact wrong)
Sent from my HTC PH39100 using Tapatalk
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
hackit said:
I have a raider from rogers and tried putting the PH39IMG zip on my htc sd drive and get an error about wrong img (or something to that effect).
So is this for the at&t vivid only?
as I still have cwm from the original raider thread for rogers, bell, fido from here.
and this appears to be updated and backing up to the ext-sd, which is much better.
Click to expand...
Click to collapse
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Thanks will try now.
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
---------- Post added at 09:01 PM ---------- Previous post was at 08:29 PM ----------
Worked like a charm, just finished my first nandroid backup as well.
off we go to start testing out a rom.....
wooo hoooo!
Pirateghost said:
no, just fastboot flash the new recovery img. the PH39 method isnt working right now for some reason.
Click to expand...
Click to collapse
ok i have a question, after using the phone for a full day know (still stock).
I have noticed I'm unable to keep my connection to rogers for data only.
I have checked and the apn is right.
I have cleared dalvic cache and fixed permissions.
Still when im away from wifi and using data, most of the time i have no connection.
Now before i updated to this version of cwm i had no issue's with my data connection.
anyone else having an issue with a raider on rogers?
Thanks

Using TWRP but can't Flash to stock

Hey guys, new to the forum but been lurking around and trying different roms, it's my first time using TWRP and I want to flash back to stock. It seems like every time I try to flash it's telling me it's failed.
pipicalsi said:
Hey guys, new to the forum but been lurking around and trying different roms, it's my first time using TWRP and I want to flash back to stock. It seems like every time I try to flash it's telling me it's failed.
Click to expand...
Click to collapse
Did you try to re-download the file?
meekrawb said:
Did you try to re-download the file?
Click to expand...
Click to collapse
I have and it's still telling me it's failed.
pipicalsi said:
I have and it's still telling me it's failed.
Click to expand...
Click to collapse
try installing twrp again
ReckYoChips said:
try installing twrp again
Click to expand...
Click to collapse
How can I do that?
pipicalsi said:
I have and it's still telling me it's failed.
Click to expand...
Click to collapse
Are you downloading it with your phone? Download to your PC and move it to your phone.
was enticts
meekrawb said:
Are you downloading it with your phone? Download to your PC and move it to your phone.
Click to expand...
Click to collapse
I just did that and did a full wipe. It's still saying failed, I can't seem to find out what's the problem. Only having issue flashing to stock but everything else seems to be fine.
good luck with that. best thing I can suggest is try some different button combos. try a different order of operations some how. in twrp, full wipe, system reset, then reboot back into recovery, another wipe /reset and then flash. that's the extent of my knowledge. you said you redownloaded the stock files to flash...maybe find a different place to download it from, could have downloaded a bad file twice?
Are you using the one from the wiki? I just tried it with TWRP 2.5.0.0 and it worked fine.
meekrawb said:
Are you using the one from the wiki? I just tried it with TWRP 2.5.0.0 and it worked fine.
Click to expand...
Click to collapse
Yeah that's where I downloaded the file and I'm also using TWRP v2.5.0.0
I don't really know how to take a screenshot in recovery but I'll type in what it says.
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/external_sd/uvlg3.flash2sotck.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sd/uvlg3.flashtostock.zip'.
Updating partition details...
At this point it'll say Zip install Complete
But the word Failed is written in Red underneath the Home icon.
Hope this helps. Also when I try to flash peach sunrise, it's also giving me the same problem! Is there an alternative way to flash2stock?
Any help would be much appreciated! Thank you for you time guys.
You are probably going to have to use Odin to flash stock. It is in the wiki.
If you do need it, I posted a copy of Odin for our phone in this thread:
http://forum.xda-developers.com/showthread.php?t=2307264
You should probably try to Odin flash TWRP first and see if that fixes it.
http://forum.xda-developers.com/showpost.php?p=41869680&postcount=13
Warning: Odin can damage your phone if used improperly. I will walk you through if you need it.
meekrawb said:
You are probably going to have to use Odin to flash stock. It is in the wiki.
If you do need it, I posted a copy of Odin for our phone in this thread:
http://forum.xda-developers.com/showthread.php?t=2307264
You should probably try to Odin flash TWRP first and see if that fixes it.
http://forum.xda-developers.com/showpost.php?p=41869680&postcount=13
Warning: Odin can damage your phone if used improperly. I will walk you through if you need it.
Click to expand...
Click to collapse
I've flashed using Odin before a while ago when my phone was bricked. I'll have to read this over again and give it a shot. I'll let you know if I need help, thank you so much for your time meek! I appreciate it, I'll let you know how it goes after flashing TWRP with Odin.
Reset your TWRP settings, also, try downloading with a different browser and try under linux. Some browsers and anti-virus have issues with android files and delete them without warning.
Thank you so much for your help guys! I got it to work by flashing using Odin. I'm having a little bit of an issue though, every time my phone dies it starts having problems with the external memory. Like for example, my phone dies and I try to open my camera it'll tell me "not enough space blah blah" and when I try to change the settings through the camera, it just force closes. Not only for the camera, also other apps that need external storage like waze. It won't let me use the GPS because there's no memory. Mind you, I have a 16gb sd card in the phone. Any fix for this situation?
Using AOIP Linaro ROM btw. I couldn't post at the original thread because of my low post count so I'm hoping I get some help here.
Thanks you guys for the help! I really appreciate it.

[Q] Stuck on Splash Screen

Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
TheSignor said:
Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
Click to expand...
Click to collapse
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
TheSignor said:
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
Click to expand...
Click to collapse
Look here Q14
bigdaddy619 said:
Look here Q14
Click to expand...
Click to collapse
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
TheSignor said:
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
Click to expand...
Click to collapse
TBH I only use sense roms ask your question in the 4.2.2 > 4.1.2 thread

Help Encryption unsuccessful error

So to set the story i had came home and rooted jb via linux method. Then presumed to use bootstrap as a recovery. I installed it and it said success. Then i presumed to change the bootloader unknowing if it was locked. So i reboot and i am stuck at Encryption unsuccessful screen and the only option is to power off or reset. What do i do ive tried to reset but it doesnt work also i tried to do a hard reset via stock recovery this also didnt work im unsure where to go about this problem now. Please help Im panicing! From what ive researched i think its soft bricked. Also there appears to be a fix on House of Bionic but it isnt clear. Lastly, I believe the problem resides with bootstrap but im unsure its just a hunch. All options will be tried.
CVanB said:
So to set the story i had came home and rooted jb via linux method. Then presumed to use bootstrap as a recovery. I installed it and it said success. Then i presumed to change the bootloader unknowing if it was locked. So i reboot and i am stuck at Encryption unsuccessful screen and the only option is to power off or reset. What do i do ive tried to reset but it doesnt work also i tried to do a hard reset via stock recovery this also didnt work im unsure where to go about this problem now. Please help Im panicing! From what ive researched i think its soft bricked. Also there appears to be a fix on House of Bionic but it isnt clear. Lastly, I believe the problem resides with bootstrap but im unsure its just a hunch. All options will be tried.
Click to expand...
Click to collapse
I had something similar happen when I first rooted my Bionic and all I did was just reflashed my phone back to stock 4.1.2 and started fresh. Not sure about any other options as I needed to get my phone back in a hurry
lancelinksp said:
I had something similar happen when I first rooted my Bionic and all I did was just reflashed my phone back to stock 4.1.2 and started fresh. Not sure about any other options as I needed to get my phone back in a hurry
Click to expand...
Click to collapse
How would i go about doing that. Would i use the stock recovery?
CVanB said:
How would i go about doing that. Would i use the stock recovery?
Click to expand...
Click to collapse
Its been a while since I have had to do it but you should use RSD Lite and a 4.1.2 hsx file for the bionic. If you google the two you should comeup with the files you will need. Sorry I cant be of more help.
EDIT: So I still have the file you need to flash using RSD Lite (Not sure what version you will need). https://dl.dropboxusercontent.com/u/80936776/cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip This file is 468 MB.
Now you just need to download RSD Lite. It only works with Windows. Windows XP is probably your best bet.
lancelinksp said:
Its been a while since I have had to do it but you should use RSD Lite and a 4.1.2 hsx file for the bionic. If you google the two you should comeup with the files you will need. Sorry I cant be of more help.
EDIT: So I still have the file you need to flash using RSD Lite (Not sure what version you will need). https://dl.dropboxusercontent.com/u/80936776/cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip This file is 468 MB.
Now you just need to download RSD Lite. It only works with Windows. Windows XP is probably your best bet.
Click to expand...
Click to collapse
Thanks im gonna try it out right now and ill let you know how it goes
CVanB said:
Thanks im gonna try it out right now and ill let you know how it goes
Click to expand...
Click to collapse
Well i tried it and got stuck at step 4
CVanB said:
Well i tried it and got stuck at step 4
Click to expand...
Click to collapse
UPDATE: I went into the xml file and deleted the oem step both clear and set now it is running without error :victory: just gotta wait for it to finish and ill keep updated to the end result
CVanB said:
UPDATE: I went into the xml file and deleted the oem step both clear and set now it is running without error :victory: just gotta wait for it to finish and ill keep updated to the end result
Click to expand...
Click to collapse
Did you use the file I sent a link for or did you download a different one? I could of sworn I modifed the xml and so that it wouldnt error out. Well, did you get it working completely then?
lancelinksp said:
Did you use the file I sent a link for or did you download a different one? I could of sworn I modifed the xml and so that it wouldnt error out. Well, did you get it working completely then?
Click to expand...
Click to collapse
Yes I believe you did edit it out. However I used a different link. I did get it working and rooted with the help of a linux bootable disc. Also I install safestrap correctly. But ran into a problem. I got cocky and didnt read all the instructions on flashing a rom and accidently flashed it over top of the stock rom so when i boot it loops then goes to recovery. Next i did a factory reset and wipe retried but no luck. So i did the only thing i knew to do was to make a second rom slot and install the backup i made of the stock. Which works fine no complaints. But low on storage how would i go about wiping the stock rom with out doing a complete factory reset through rsd lite again. That way i could just flash my backup on top of stock cause it wont flash properly as is. Thanks in advance
CVanB said:
Yes I believe you did edit it out. However I used a different link. I did get it working and rooted with the help of a linux bootable disc. Also I install safestrap correctly. But ran into a problem. I got cocky and didnt read all the instructions on flashing a rom and accidently flashed it over top of the stock rom so when i boot it loops then goes to recovery. Next i did a factory reset and wipe retried but no luck. So i did the only thing i knew to do was to make a second rom slot and install the backup i made of the stock. Which works fine no complaints. But low on storage how would i go about wiping the stock rom with out doing a complete factory reset through rsd lite again. That way i could just flash my backup on top of stock cause it wont flash properly as is. Thanks in advance
Click to expand...
Click to collapse
Activate the stock slot, then go to advanced wipe and select cache, dalvik cache and system. Then after the wipe you should be able to restore your stock backup to the stock slot. Then reboot. If it works you can then safely delete the other slot you created.

Categories

Resources