Database Develop

[Q] Stock restore fails, but I won't give up! (Help please)

So I'm trying to get my VZN Galaxy Tab back on its feet. After trying to get Gingerbread in it so I can use Netflix - and failing - I'm going through a lot of motions.
Okay. First I rooted it with Super One Click. I should have been happy with that, but noooo. Then I tried flashing GB on it (I wish I can remember which ROM I started with...it's a mess. I think the pit file was gt-p1000_mr? Does that sound right?).
When that didn't work, I went to the much-cross-posted procedure for returning it to stock using Heimdall and SCH-i800_VZW_stock. Tried it five times. Each time, it booted into the Galaxy Tab/Samsung logos, then a fast glimpse of scrambled letters for a second followed by twinkly music, then black nothingness. It would then bootloop. I attempted to boot into recovery to wipe data/cache, but I couldn't get there. Vol-Up/Pwr just brought up the logo and scrambled video again.
Since I was still able to get into download mode, I tried flashing another ROM...this one the "P1000XXJQ1_P1000XXJQ1_P1000XXJPZ" method. With this, I was able to also flash CWM so I have SOME recovery mode. Sadly, booting brings up the GT/SAMSUNG logos and I get the spacey animation, but after that, again - blackness. This time, however, the Menu/Home/Back/Search buttons light up, so something's happening in there.
Also, booting into CWM, I cannot get my sdcard to be recognized. I tried different cards, so there's something goofy with the slot itself, I'm guessing.
So nothing is really working, but since I can get into CWM and also download modes, I'm holding out hope that this is not completely bricked.
I just need to find the right method of getting it back to a functioning tablet. If anyone has any suggestions, I'm all eyes. Thanks so much.
UPDATE: I tried reflashing stock using the tried and true method. But this time, I went in and flashed CWM replacing the stock recovery which never worked for me. I got the Galaxy Tab/Samsung logo, and at long last, the animated VZW logo. Then it would bootloop there. I booted into CWM recovery and wiped the data/system and the cache from the first page. It still booted and bootlooped the same. This time, I booted into recovery, went to the mounts and storage section and formatted the system, data and cache. Opening logo only. CWM again, and got a whole bunch of "cache missing" messages. But I think I'm getting closer. Back to work.
UPDATE II: So the farthest I can get is the animated VZW logo using the combo of the stock flash through Heimdall, then flashing CWM with Odin. Still no sdcard access. Anything I should try here? Thanks.

same question here
Did anyone figure out how to restore Verizon tab?

Stuck on Boot Screen

Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks

I've read you can hook up to your pc and mount your sdcard from cwm. Never tried it but if it works you can save your data that way then maybe a master clear/cache or dalvik wipe will help.
Sent from my SAMSUNG-SGH-I897 using XDA App

BumRush said:
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
Click to expand...
Click to collapse
You can mount USB in recovery and get all your stuff off of your SD that way. You can also nandroid your current ROM in CWM and re-flash it, then restore from backup. As far as saving texts and all that, Idk if you can, but I'm sure someone else does.
Also, you could try clearing dalvik, cache, and then running the kernel cleaning script. It's gotten me out of a few binds before. It might help you to where you wouldn't have to flash again.

[Q] Cannot get past splash screen, CAN access clockworkmod

If anybody can help me, I would be very grateful, I'm totally stuck at this point. I think I am having problem with the boot image.
I just tried to flash Revolt Rom 1.3. I previously had Revolt 1.1 and decrapified before that.
I followed the same procedure as before, but cannot get my phone to boot. I just get LG screen > splash screen > Verizon 4G LTE Screen > backlit blank screen and pulsed vibration.
I can get into clockwork mod and see my backups. I tried to flash backups, Revolt ROM 1.1, and Decrapified several times to no avail.
Here is my step by step using decrapified
1) Hold down volume and power (I get permanently Erase Screen)
2) Confirm twice ( I get lg screen then clockwork mod)
3) go to back up and restore > advanced restore > revo_decrap-1.1 > restore system > yes- Restore system
***Sometimes I just get "restore complete!" Sometimes I get "error while flashing boot" But restore seems to go normally***
4) Go to advanced > Wipe Dalvik Cache > Confirm wipe Dalvik Cache (I get Dalvik Cache wiped)
5)+++++Go back+++++ > Reboot System Now ( I get same problem)
Any help is much appreciated!!!
mobiusnc

mobiusnc said:
If anybody can help me, I would be very grateful, I'm totally stuck at this point. I think I am having problem with the boot image.
I just tried to flash Revolt Rom 1.3. I previously had Revolt 1.1 and decrapified before that.
I followed the same procedure as before, but cannot get my phone to boot. I just get LG screen > splash screen > Verizon 4G LTE Screen > backlit blank screen and pulsed vibration.
I can get into clockwork mod and see my backups. I tried to flash backups, Revolt ROM 1.1, and Decrapified several times to no avail.
Here is my step by step using decrapified
1) Hold down volume and power (I get permanently Erase Screen)
2) Confirm twice ( I get lg screen then clockwork mod)
3) go to back up and restore > advanced restore > revo_decrap-1.1 > restore system > yes- Restore system
***Sometimes I just get "restore complete!" Sometimes I get "error while flashing boot" But restore seems to go normally***
4) Go to advanced > Wipe Dalvik Cache > Confirm wipe Dalvik Cache (I get Dalvik Cache wiped)
5)+++++Go back+++++ > Reboot System Now ( I get same problem)
Any help is much appreciated!!!
mobiusnc
Click to expand...
Click to collapse
Try to use a full recovery from before you flashed the newest update. That will have the full everything including the old boot.img that was working for you. After that reflash the ROM you want as system and everything should be perfect.
Hope this helped.

Haro912 said:
Try to use a full recovery from before you flashed the newest update. That will have the full everything including the old boot.img that was working for you. After that reflash the ROM you want as system and everything should be perfect.
Hope this helped.
Click to expand...
Click to collapse
Thanks for the help. I'm assuming you mean just restore? Not advanced restore of any kind?
I just tried "backup and restore > restore > choose a date > confirm" but unfortunately it didn't help. There were no errors in the restore process. I'll try again with an earlier backup( I have 3 total)
Anything else I could try?
Thanks,
mobiusnc

I just did the same process with an earlier backup (decrapified) and it worked! Not sure what I did differently....but it worked!
Thanks a lot. I really appreciate it, I was getting very worried...
mobiusnc

Any time dude. Also, I try to keep myself in the habit of backing up before flashing a new ROM and then a few days after installing the new one back up that one. I have a folder on my computer with older versions and I keep a few on my phone as well. I have had to lose a few days before and I hated having to change everything backto how I had it and stuff. I'm stoked I could help you out though.

Hmmm, there still seems to be an issue. I was able to recover to a backup of decrapified. Everything looked good. Then I tried to reflash Revolt1.1, which I had before. I get the blank backlit screen with vibration pulses.
Another clue might be that I only get the 4G "jingle" with the backed up version. Other times it is silent during bootup.
Very strange....any ideas anyone?
I hope I'm not stuck with decrapified-1.1 for ever! I was having problems with the pushed update basically causing the same blank backlit screen with pulse issue. Next I'm going to try the stock rooted rom provided by thecube. Then bed...
mobiusnc

I was able to get the rooted stock ROM to work using just "restore", not "advanced restore > system". It does not work using the latter. At least it's a start.
Is there a difference in the boot images between ROMs? I'm guessing yes. If so, could somebody create a boot image for Revolt 1.3? I'd love to try and see if I can get it to work using regular "restore" with a boot image.
mobiusnc

No ROMs other than stock have a boot.img yet. You just have to have the 2 files for the ROM in a folder and then adv restore them to system. If you can get into one of the Revolt ROMs the OTA will no longer be pushed to your phone and I believe you will have it without losing root. Not 100% on that though.

The jingle was cut from Revolt to shave down the size of the install.
Sent from my VS910 4G using XDA Premium App

Try doing a data wipe and then try again
Sent from my VS910 4G using XDA App

Me too
I run into this problem with mine every few days. I am able to get up and running by restoring a backup... but that gets annoying. I also returned my first Revolution to Verizon because of this issue. So far I haven't figured out what's causing it. It usually happens when the phone is just sitting in standby minding its own business, then spontaneously reboots to the blank screen. I'll keep experimenting.

New ROM Gone Wrong!

Okay so basically yesterday I got my lovely spanking HTC ONE (m7) and quickly proceeded to downloading the One_All-In-One_Kit, uncloked the bootloader and rooted the phone successfully.
I then proceeded to download ARHD and flash it accordingly, everything went swimmingly, the ROM installed via Aroma as it should, yep all nice and dandy. NO! After the installation, I rebooted, get to the HTC bootscreen, I'm presented with a nice new red message at the bottom and then the phone restarts itself, tries to enter recovery, that doesn't work, then it tries booting up again and does the same thing over and over.
I've flashed the ROM several times and get the same thing each time. I've tried RGUI and get the same sort of thing with that only with RGUI the phone doesn't try rebooting into recovery it just stays on the HTC bootscreen.
I'm desperate for help on this so please, if anyone has any insight it would be highly appreciated.

I hope you're not also flashing any of the custom kernels on here....cos they're not compatible with 4.2.2

Nope not flashing anything else but the ROM itself..

after flashing did you try "fastboot erase cache" ?
sometimes that helps when phones get stuck on the HTC logo after a rom flash.

Use the toolkit to erase cache
Sent from my HTC One using xda premium

Yeah done that several times too. Can't seem to work out why it isn't working and I too can't find the correct RUU for my device meaning I can't even take it back to stock

try to hold power + volume down to get into the bootloader to get back into recovery. Once in recovery factory reset, erase cache, erase dalvik, and reflash the rom.
also download the andorid SDK for fastboot and adb, then try "adb reboot bootloader" if you can not get back into the bootloader to get into recovery
My friend had his do this loop as well, we had trouble getting it into recovery, but held the button combo of power and vol down several times (probably 10) and it FINALLY booted into the custom Clockwork recovery, then we reflashed and it worked like a charm.

Also try redownloading... it could be a bad download
Sent from my Nexus 10 using Tapatalk HD

rilee said:
Okay so basically yesterday I got my lovely spanking HTC ONE (m7) and quickly proceeded to downloading the One_All-In-One_Kit, uncloked the bootloader and rooted the phone successfully.
I then proceeded to download ARHD and flash it accordingly, everything went swimmingly, the ROM installed via Aroma as it should, yep all nice and dandy. NO! After the installation, I rebooted, get to the HTC bootscreen, I'm presented with a nice new red message at the bottom and then the phone restarts itself, tries to enter recovery, that doesn't work, then it tries booting up again and does the same thing over and over.
I've flashed the ROM several times and get the same thing each time. I've tried RGUI and get the same sort of thing with that only with RGUI the phone doesn't try rebooting into recovery it just stays on the HTC bootscreen.
I'm desperate for help on this so please, if anyone has any insight it would be highly appreciated.
Click to expand...
Click to collapse
Just a word of advice. Update your profile to say your country and carrier. It helps people identify which device model and carrier you use.

Thanks for the help so far guys, basically I can get into recovery, that's not the problem, the problem is the phone gets stuck on the HTC screen after the ROM has been installed. I'll try downloading the ROM again when I can, in the hope that it is just a bad download. Hopefully this is the case and re-flashing a newly downloaded ROM will solve all my issues.
I'll post back with the result as and when I can.

rilee said:
Thanks for the help so far guys, basically I can get into recovery, that's not the problem, the problem is the phone gets stuck on the HTC screen after the ROM has been installed. I'll try downloading the ROM again when I can, in the hope that it is just a bad download. Hopefully this is the case and re-flashing a newly downloaded ROM will solve all my issues.
I'll post back with the result as and when I can.
Click to expand...
Click to collapse
I would be restoring my nandroid backup and make sure the phones that way first and then start again

Thanks again for the help guys, went to phones 4 u this afternoon and he exchanged the device for me.

Solved - Locked Boot Screen, Unable To Access Custom Recovery Image.

Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.

*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.

Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app

Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX

http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app

SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.

Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.

When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.

SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.